Neowin.net

LOL! That was a classic.
http://www.firefoxflicks.com/flick/index.p...542&c=false

It means they did something nice for a minority.

Yup. Since I got my Mac I had always used Safari because it was the best...until Firefox 2.0 came out. Since then Firefox 2.0 is much much faster then Safari and has a better interface.

Oh, I got confused; I wrote that this morning and I was sick this morning... I thought they meant Dashboard

They should have said Cocoa widgets, though...

Safari 3 should be comparable to Firefox 2, as it adds some new features, like tab reordering and some advanced widget management.

Gecko 1.9 Alpha 2 introduces several new features which can be tested by using Gran Paradiso Alpha 2:

* Core layout code affecting the calculation of widths in tables, floats, and absolutely positioned elements has been rewritten. The code for handling incremental layout of pages (as data arrives over the network, as images load, or as dynamic changes are made) has also been changed extensively. (See the Reflow-Refactoring wiki page for more information.
* Resolved remaining issues with ACID2 test compliance.
* Support for the Web Apps 1.0 API for changing stylesheets.
* The inline-block and inline-table values of CSS 2.1's display property are now implemented.
* XML documents can now be rendered as they're downloaded instead of only after the full document has been loaded.
* Greatly improved Mac widgets support since Alpha 1.
* Improvements in the Cairo graphics layer.

I've noticed the 1st change greatly... especially the calulation of tables and floats. Pages that never looked right now do.

MozBackup your current FF install

This isn't a bug, but a feature.

Firefox works by caching the most resent pages/images that you've visited, so that the user gets the pages more quickly when returning.

A study shows that people often use the back-button, and then visit pages in the cach for faster rendering.

Nothing to 'fix'. You can manually adjust the memory usage for your Firefox. You trade-off page load time for memory usage.

I think they added a new way to cache, although I might be imagining things.

One of the new things that's gone into Gecko 1.9 is an XPCOM Cycle Collector, which basically acts as a garbage collection mechanism for XPCOM objects. Right now it isn't making much of a difference since it's in a pretty raw state of being at the moment, but I think once it gets refined and more components are coded to use it, it could make a big difference in the overall memory footprint. Also, some of the larger patches that have landed have greatly simplified large sections of code, which will also help with memory footprint. Finally, more work is being done on the image rendering side of things. I know there's a patch in review right now which has the potential to dramatically cut down on the memory (and CPU) usage spike caused by the loading of animated GIFs.

All in all, I think you'll find that by the time Firefox 3.0 ships, the memory situation will certainly be improved from where it's at now. Obviously there'll always be room to improve, but I can say with absolute certainty that there are developers who take footprint very seriously and are working hard on improving things.

Yes, it passes: http://arstechnica.com/news.ars/post/20061212-8409.html

Read.Comprehend.Post

From the article summary: "(...) and the addition of full support for ACID2 test compliance."

indeed. RTFA

I hope for that too.. Becomes pretty annoying from time to time.

I'm no Mozilla employee, nor am I a Firefox developer. And I certainly cannot claim to be familiar with most of the Firefox code. Nor am I involved with the development process, let alone have used Firefox for more than a week since it first began. But, I can safely tell you that writing a multi-threaded SIMD interface is hard.