New Skin and Another Big Change!
Tuesday October 26th, 1999
The new skin is in the 10-26 builds. Visit our builds page to get the latest. I find myself not minding the whitespace around the sidebar's border as much as I expected I would. However, there is one issue that troubles me. When you move the sidebar's "splitter", instead of moving a "ghost" of the splitter, you move the splitter itself. the problem is that if you're expanding the sidebar, the splitter disengages from the top and bottom border of the sidebar, leaving a white gap. If you shrink the width of the sidebar, the splitter moves past the right edge of the top and bottom borders of the sidebar, and the effect is just as bad. The answer would be to either 1) expand and contract the sidebar in realtime as the splitter is moved (probably slow), or 2) manipulate a "ghost" of the splitter during resize, and when the mouse button is released, move the actual splitter and resize the sidebar.
The second bit of news is that they've made more changes to the "incremental reflow" of the rendering engine. Now, the page will start rendering content even before reaching closing tags. This means a dramatic decrease in the time taken to get content displayed, and it's a great benefit when loading pages with long lists of data. But I find the content shifting disconcerting (check out mozilla.org, mozillazine.org and slashdot.org for examples if you have a 56k connection or slower), and the decrease in scrollbar responsiveness is vexing. Hopefully that will be working on these issues in the coming weeks leading up to the beta.
#65 Wheel mice do not work with the new scrollbars
Thursday November 4th, 1999 6:50 AM
You are replying to this message
If you turn on the gfx scrollbars in mozilla rather than use the platform specific scrollbars you have a few major problems: 1) Wheel mice don't work with these scrollbars 2) The look and feel of the scrollbars are different to other applications. 3) If you're using a themable OS (e.g. Linux running GNOME) then the scrollbar won't change to match the theme that you're using.
Basically we need to make a browser that acknowledges the users preferences across the OS which in the case of Linux means respect any GTK themes, and in MacOS and Windows respect any default colour preferences, etc.
In XUL (I don't know if there is already) there should be options that can be set to OS default.
So for example you can write a theme that uses the OS default options for some characteristics but the theme for others.