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."

Comments

Re:What new features in 1.1?

[goofyspouse]

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)

Re:Composer?

[Jack Comics]

Your solution is at hand. NVU is a multi-platform "spin-off" of Mozilla Composer, based on the Gecko 1.7.5 engine used by the Mozilla Suite and Firefox 1.0.

Re:What new features in 1.1?

[davron05]

From the Unofficial Firefox 1.1 changelog:
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 - :active neither hierarchical nor picky about what can be activated.
* 175893 - Make XUL 's focusable.
* 20022 - :hover state not set until mouse move.
* 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 .dmg internal zlib-compression, not .dmg.gz.
* 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=2175 27). Copy&paste the link to your browser since diredt linking to bugzilla from slashdot doesn't work.

Re:But can it render Slashdot?

[md27]

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.

Where's the freakin' roadmap??

[amake]

If you wanted to see the actual roadmap itself, starting at this /. article you had to wade through not one, not two, but three intermediate sites to get to it. Thanks a lot for not putting a direct link anywhere in the article, guys.

Re:Firefox security updates?

[algae]

I'm using FireFox 1.0, and everytime i've seen a security hole announced, an auto-updater pops up within a day or so to install the hot-fix. It's a little green arrow right under the title bar.

Re:Safari Innards

[TheRaven64]

The rendering engine in Safari is WebCore, which is based on KHTML, from the KDE project. A large number of changes have been made by Apple, many of which have not found their way back into KHTML yet (because KHTML is understaffed and can't handle the merging, not because Apple is hoarding them). While it is similar to Gecko in terms of features, I have found that it has slightly better CSS support[1], and produces nicer looking[2] output for several attributes (I seem to recall that bevelled boarders being one of them, although I may be wrong).

WebCore is open source, but it is written in Objective-C++ (core is C++, interface is Objective-C), which is currently only supported by GCC on OS X (mainly due to the size of the maintainers' egos). Once the main branch of GCC gets Objective-C++ support, it is probable that the GNUstep project will gain a WebCore based browser.

[1] Not in any way an objective measurement, I've just found that a few CSS tags I've wanted to use have been supported by Safari but not by anything else including Gecko.
[2] Again, 100% subjective.

Re:SVG?

[wikinerd]

About SVG: If you read my article on Mozilla 1.8 Alpha 6 you will see that I mention "Improved support for SVG". So, Mozilla 1.8 already has better SVG support.