I've already come across a few rendering enhancements and bug fixes to the Mozilla's gecko engine as of Firefox 1.5. For instance, I designed this menu system that uses javascript to attach menus that hang out in a really high z-index (above the rest of the page) to an item in the menu header on mouseover and I use the same idea and functions to attach something I call 'action menus' to readonly text fields I use that only allow a user to lookup the value in a separate search area rather than manually enter a value. In Firefox 1.0x, I had to use a different values in my javascript depending on what I was attaching the menu to (the top menu or a readonly text field). I had to use different values because if I attached the menu directly to the bottom of the the text field (like I did the td element that housed the main menu item), the menu would actually float about 2 pixles below the text field. The problem here is that the menu should appear when you mouseover the text field and disappear when you mouseout of the text field OR mouseout of the menu. With a 2 pixel gap between the text field and the menu, the user's mouse could never get to the menu without the menu disappearing. because of the mouseout of the textfield. Needless to say, Firefox 1.5 fixed this as I noticed that when I started testing with the release candidates, my action menu was displaying about 2 pixels higher than the bottom of the text field (which was the hack to get it to sit at the bottom before 1.5).

Another fix is that a scrollable div, which uses overflow-y:scroll, that I use for some AJAX goodness doesn't work at all in Firefox 1.0x. Perhaps simply overflow works. Either way, overflow-y was the best option for this div because I wanted to make sure that the content inside wouldn't scroll horizontally (because honestly, horizontal scrolling is so ugly). Thank you for a great browser! Sincerely, me