Browser Wars II: The Saga Continues
adamsmith_uk writes "For the first time in three years something has happened in browser land. In fact, major events have started happening at a breathtaking pace. Time for a long overview that tells the whole story. "
I really miss the "Software war" map which used to be at atai.org
The last update has been 2002 and it never got updated since.
Agreed - at work we recently had a query about spam and popups. Two or three of us suggested using Mozilla or Netscape instead of IE. We pointed out the ability to suppress popups and minimise email spam within the Netscape mailer in addition to the lower chances of viruses.
To put it mildly we were howled down. People wanted to continue with IE and Outlook. They were happy to add absurd bits of additional software to stop duff information getting as far as IE and Outlook, but they weren't prepared to change them.
I hate to break this to you, but Netscape *is* Mozilla, with some branding added to it, and the odd feature to link in with AOL... but most of the development for Netscape is done by the Mozilla team (who incidently, has a sizable proportion of Netscape employees paid to work for them).
OK then. Here are some features that *were* added to Mozilla in the last year.
- NTLM support
- open multiple home pages in tabs
- per-site popup blocking
- rich-edit control (Midas)
- image auto-sizing
- dynamic profile switching
- find as you type
- bookmark groups
- XML prettyprinting
- WSDL support
- composer has image and table resizing
- junk mail controls
- link prefetching
- more info on Page Info panel
- extra tab browsing options
- download manager improvements
- more intelligent autocomplete
- view selection source
Firebird is based on the Mozilla rendering engine, right?
... http://bugzilla.mozilla.org/show_bug.cgi?id=33339, although I personally am not aware of its actual status.
Yes.
The one without a full, documented API that enables you to actually do things to the content, right?
The W3C DOM API compliant one, which is very well documented and implemented closer to the standard than IE.
The one that doesn't allow you to get actual rendered layout values?
Again, its W3C DOM compliant.
The one that doesn't support the ruby tag?
The "RUBY" tag was recommended to the W3C in 2001 and became part of XHTML 1.1. They're working on it
Skiers and Riders -- http://www.snowjournal.com