Skip to main content

Firefox 3 gets the bugs out...

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.


Comments

Popular posts from this blog

the attributes of web 3.0...

As the US economy continues to suffer the doldrums of stagnant investment in many industries, belt tightening budgets in many of the largest cities and continuous rounds of lay offs at some of the oldest of corporations, it is little comfort to those suffering through economic problems that what is happening now, has happened before. True, the severity of the downturn might have been different but the common factors of people and businesses being forced to do more with less is the theme of the times. Like environmental shocks to an ecosystem, stresses to the economic system lead to people hunkering down to last the storm, but it is instructive to realize that during the storm, all that idle time in the shelter affords people the ability to solve previous or existing problems. Likewise, economic downturns enable enterprising individuals and corporations the ability to make bold decisions with regard to marketing , sales or product focus that can lead to incredible gains as the economic

How many cofactors for inducing expression of every cell type?

Another revolution in iPSC technology announced: "Also known as iPS cells, these cells can become virtually any cell type in the human body -- just like embryonic stem cells. Then last year, Gladstone Senior Investigator Sheng Ding, PhD, announced that he had used a combination of small molecules and genetic factors to transform skin cells directly into neural stem cells. Today, Dr. Huang takes a new tack by using one genetic factor -- Sox2 -- to directly reprogram one cell type into another without reverting to the pluripotent state." -- So the method invented by Yamanaka is now refined to rely only 1 cofactor and b) directly generate the target cell type from the source cell type (skin to neuron) without the stem like intermediate stage.  It also mentions that oncogenic triggering was eliminated in their testing. Now comparative methods can be used to discover other types...the question is..is Sox2 critical for all types? It may be that skin to neuron relies on Sox2

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform cert