Slashdot Mirror
Mozilla Roadmap Update
wikinerd writes "According to a recent roadmap update for Mozilla, the beta 1.8 version will be unveiled this month, while in the next month a second beta will be prepared. After the Beta2, Gecko engine 1.8 will be finished and it will power Mozilla 1.8, Mozilla Firefox 1.1 and Mozilla Thunderbird 1.1. The developers will then start working on Mozilla 1.9. Here are some nice graphics depicting the roadmap."
$lt;br> problem!) but it's a free WYSYWIG HTML editor withoout too many frills or complexities, and it throws out reasonably tidy HTML which can be cleaned up by hand much more easily than (say) Frontpage output.
So what's the future for Composer? I'd love to have it either as a standalone alongside Firefox and Thunderbird, or as an extension to Firefox.
I notice that Thunderbird contains vestiges of Composer (e.g. CSS styles for display modes no longer available)...
From http://www.mozilla.org/projects/firefox/roadmap.ht ml :
... ?
We are still working on goals for 2.0 and are drafting a PRD for its development. Some likely goals include:
* Improvements to Bookmarks/History
* Per-Site Options
* Enhancements to the Extensions system, Find Toolbar, Software Update, Search and other areas.
* Accessibility compliance
* More
(Note: placing an item on this list does not mean it will not be complete until 2.0, rather we would like to be done by 2.0, it may be implemented by 1.1, 1.5 or 2.0)
The Mozilla Suite may not be disbanded, but how many people even know about it anyway? Its got its little niche, but whether or not it truly "goes away" now seems irrelevant. Firefox is the focus of all the publicity, and the Suite goes on about its business on its own.
They should make the gecko do the robot in the about window.
I don't see Sunbird in any of those slides. We still seem to be far away from a complete Outlook replacement that is stable enough to pitch to people. I would think replacing Outlook would be a good investment of resources.
Firefox is an attempt at seperating the browser component of Mozilla, and hopefully making it smaller, more portable, and more memory-efficient.
The rendering engine for both Seamonkey (the Mozilla Suite) and Firefox remains the same, the Gecko rendering engine. What differs is the UI, the functionality and large parts of the codebase.
Originally, Firefox, and Thunderbird, were scheduled to replace Seamonkey, but after some developers voiced their concerns over this, the Mozilla Foundation has decided against this move.
In short, it's not so much as code fork as it is a functionality fork. Firefox is geared towards IE/Opera/Safari users, while Seamonkey is geared towards old school Navigator/Netscape/Mozilla users.
From the Unofficial Firefox 1.1 changelog:
:active neither hierarchical nor picky about what can be activated. :hover state not set until mouse move. .dmg internal zlib-compression, not .dmg.gz.
5 27). Copy&paste the link to your browser since diredt linking to bugzilla from slashdot doesn't work.
New features
* 245392 - Installer options for where to put start menu / desktop / quick launch shortcut icons.
* 231062 - Provide Firefox MSI package.
Major improvements
* 124561 - Anonymous ftp login failure should prompt for username/password.
* 98564 - Caret overlaps the last character in textfield (if positioned after the last char).
* 151375 - Focus outline should be drawn outside of element.
* 133165 - Focus outline should include larger descendants of inline elements.
* 65917 -
* 175893 - Make XUL 's focusable.
* 20022 -
* 276588 - Rework toolkit command-line handling. You can now open local files easily from the command-line (e.g. firefox.exe README.txt), and command-line switches should do the same thing whether Firefox is running or not.
* 95227 - Make it possible to set different default font type (serif vs sans serif) for different languages.
* 16940 - [Windows] IME is now disabled for password fields.
* 151249 - [Mac] Middle click on link does nothing on Mac OS X (should open link in new tab).
* 242845 - [Mac] Firefox disk image should use
* 238854 - [GTK2] Changing GNOME2 theme doesn't apply until restarting Mozilla.
And yes, they are also targeting the famous Slashdot rendering bug (https://bugzilla.mozilla.org/show_bug.cgi?id=217
The only official release of Firefox is 1.0. There are a number of outstanding security flaws in Firefox 1.0 as reported by Secunia and none have been addressed yet. I don't know if there is a nightly release that fixes these flaws, but even if there is, those are not the releases that Mom and Pop download, and it is that type of user that tends to be affected most by security flaws. Doesn't the Firefox/Mozilla team need to release a version 1.0.1 that fixes these flaws sooner rather than later? Unfortunately there is no 1.0.1 on the road map, and version 1.1 is not scheduled to be released until June, if it is on time. By then the oldest unpatched flaw, from August 2004, will be 10 months old! While the severity of current flaws is nowhere near MSIE territory, the age of unpatched flaws will be getting into MSIE territory (well, somewhat, anyway.)
--- What?
There's actually a bug in Gecko that causes the mis-render, and it's fixed in the code that will be 1.1. I saw this on the burningedge 1.1 fix list.