I downloaded the latest beta of Firefox 3 beta 4 a few days ago and installed it last night. What a difference an upgrade makes. True to the claims of vastly improved speed, Firefox 3 impressed me with what you can get out of a philosophy of constantly pursuing tight code. In addition to being faster, the new browser also uses memory more efficiently. You'll recall my post on the importance of an almost manic obsession with reducing the memory footprint of every object when coding for scalable distributed web applications, though firefox is not meant to scale or distribute outside of a single computer, the designers realized that the area of memory utilization could be used to affect a noticeable improvement to the user experience and sure enough that is the case in Firefox 3. Pages load in a snap, firefox developers talked up the improvements on the mozilla blog take a look for the specific improvements made.
One thing that I am very happy about was a bug I noticed regarding the rendering of composed div elements that call dynamic code using AJAX. In my collaboration UI , a contacts list is displayed using composed AJAX calls, up until firefox 3, the display of the contents in this dynamically loaded section was irratic, depending on the amount of content loaded sometimes the outer call would resolve before the inner content had finished rendering. Thus, the outer call would render as if there was no code inside it, the pane displayed in a collapsed state instead of expanded. I could trick it by refreshing the page several times and get it to expand, but often the next manual page refresh would recollapse the pane. I tested the issue in IE , Opera and Safari (on an IPhone!) and none of them exhibited the pane collapse bug I encountered so I was sure it was a rendering issue that Firefox had. I am happy to report that the bug is now gone in Firefox 3, logging in to an account reveals the expanded display of the users contacts as it should, following links on the page refresh the page maintaining the expanded state of the pane exactly as it was supposed to. I am not sure what change was made by Firefox to fix this (probably some issue related to caching and rendering of dynamically populated div's) but it is indeed fixed!
Shot out to the firefox 3 team for relentlessly hunting down bugs and memory issues, I believe that well designed software should get tighter with each revision and the moz dev guys seem to follow that mantra as well. Kudos guys.
One thing that I am very happy about was a bug I noticed regarding the rendering of composed div elements that call dynamic code using AJAX. In my collaboration UI , a contacts list is displayed using composed AJAX calls, up until firefox 3, the display of the contents in this dynamically loaded section was irratic, depending on the amount of content loaded sometimes the outer call would resolve before the inner content had finished rendering. Thus, the outer call would render as if there was no code inside it, the pane displayed in a collapsed state instead of expanded. I could trick it by refreshing the page several times and get it to expand, but often the next manual page refresh would recollapse the pane. I tested the issue in IE , Opera and Safari (on an IPhone!) and none of them exhibited the pane collapse bug I encountered so I was sure it was a rendering issue that Firefox had. I am happy to report that the bug is now gone in Firefox 3, logging in to an account reveals the expanded display of the users contacts as it should, following links on the page refresh the page maintaining the expanded state of the pane exactly as it was supposed to. I am not sure what change was made by Firefox to fix this (probably some issue related to caching and rendering of dynamically populated div's) but it is indeed fixed!
Shot out to the firefox 3 team for relentlessly hunting down bugs and memory issues, I believe that well designed software should get tighter with each revision and the moz dev guys seem to follow that mantra as well. Kudos guys.
Comments