Firefox's future features: 3.6, 3.7, and 4.0
MOUNTAIN VIEW, Calif.--Some new fruits of Mozilla's effort to speed Firefox development are about to arrive.
Mozilla plans to release the first beta version of 3.6 this weekend or early next week. But what exactly is coming in the new version and its successors?
Mike Shaver, Mozilla's vice president of product development, and John Lilly, Mozilla's chief executive, detailed some of the browser's future in an interview at the corporation's headquarters here. And the company has an aggressive schedule, with three releases due within about a year.
Mike Shaver, vice president of engineering at Mozilla
(Credit: Stephen Shankland/CNET)The present version of Firefox was to have been called 3.1, but with significant new features, it became Firefox 3.5--and arrived later than 3.1 had been planned. Version 3.6 is slated for release in final form this year, with 3.7 in the first half of next year and 4.0 about a year from now, Lilly said.
"We're trying to shrink these development cycles down," Shaver said.
Getting personal
One of the big changes with 3.6 is building in the Personas add-on that lets people customize the appearance of the browser. It's about as cosmetic as a change can be, but reskinning software often is popular among users who want to personalize their computers.
Under the covers but more noticeable is prioritized networking that gives the active tab the lion's share of network capacity to speed its loading. The goal is to speed up multipage restarts of the browser.
Tabs behavior will get a significant change that could throw some people off. New tabs generally will appear immediately to the right of the active tab when opened from a link, rather than at the far right of the tab strip.
Finally, Firefox 3.6 will support Open Web Font, a font format that supports compression and metadata to let the origins of a typeface be tracked down.
Support for new Windows 7 interface features, though, mostly will have to wait. "Aero Peek has landed in 3.6, but Jump Lists and download status in the Windows 7 task bar will have to wait for 3.7," according to this week's update. Aero Peek lets people see miniature versions of applications from the Windows task bar; Jump Lists spring up from applications on the task bar to let people take quick actions such as opening a recently used document or Web page.
A mock-up of Firefox 3.7 shows merged reload-stop button, the home tab, and the missing menu bar option.
(Credit: Mozilla)For 3.7, the big change will be under the covers: plug-ins such as Flash will be moved to computing processes that are separate from the main browser operation, protecting the latter from problems with the former.
"We've seen more crashing since 3.5 came out, especially in last month or so," Lilly said, pointing to problems from Web-based malware attacks and from issues with Flash. The new design also should help split Firefox up into separate tasks that can take better advantage of all the computing threads offered by multicore processors.
Also coming in 3.7 will be new graphical animation work using Scalable Vector Graphics (SVG) and Cascading Style Sheets (CSS), two Web standards. And pushing the direction in which Chrome and Safari have been so aggressive, there will be new JavaScript work.
With version 3.0, Mozilla introduced Firefox's "awesomebar," officially but infrequently called the Smart Location Bar, which can be used not only to type addresses but also to retrieve the URLs of previously visited sites. With 3.7, expect an upgrade that lets people switch among active tabs by typing in the bar.
Firefox 3.7 also will mark the arrival of some significant changes to the user interface, though final details remain under discussion. Among the likely changes: a combined stop and reload button, a home tab instead of a home button, and the ability to run with the menu bar hidden.
One superficial change Mozilla hopes will make Firefox look less "dated" is work to make the browser fit in better with Windows Vista and Windows 7. There will be some corresponding changes to Firefox's Mac OS X interface, too.
This mock-up of Firefox 4.0 shows the 'tabs-on-top' option, the side-mounted menu buttons, combined address-search bar--all Google Chrome-like features.
(Credit: Mozilla)Bigger changes come with version 4.0. There each browser tab will get its own process. "In Firefox 4 we'll have a more fully multiprocess architecture for stability and increasingly to take advantage of multiple cores," Lilly said.
Another big change will be with add-ons. One of Firefox's biggest assets is the rich array of these customization options--but a corresponding frustration is how those add-ons often break with each update to the browser.
Firefox 4 will introduce a new add-on framework under development today called Jetpack that, like Chrome's, uses Web-based technologies for add-on construction. Today's Firefox uses a foundation called XUL.
Among the other perks besides compatibility, as Mozilla sees it, Jetpack extensions are easier to write and share, and they can be updated as the browser runs without a restart. Still, it will mean a big discontinuity for programmers.
"We want for developers to want to get onto Jetpack and the Jetpack application programming interface," Shaver said, and the current plan is to drop the older add-on technology with Firefox 4.
Finally, there will be more changes to the browser's appearance. Some have called it a Chrome copy--features include a merged location bar and search bar, removing the status bar across the bottom, and adding an option to put the tabs at the very top of the browser, all features introduced with Chrome. Lilly, though, bridles at the Chrome-copy idea.
"We're trying to get as much window space as possible for content," he said. "I don't think it's a move toward Chrome. We're trying to give space to the content."
Stephen Shankland writes about a wide range of technology and products, but has a particular focus on browsers and digital photography. He joined CNET News in 1998 and since then also has covered Google, Yahoo, servers, supercomputing, Linux and open-source software, and science. E-mail Stephen, or follow him on Twitter at http://www.twitter.com/stshank. 
The coming (though still distant) "tabs on top" option a la Chrome makes more economical use of vertical real estate, too, as long as you don't cherish your title bar.
In fact, all the things up to Firefox 4.0 are already in Opera. And they're configurable so you can turn them on and off as required.
(Oh, sorry... I don't think prioritized networking is in Opera.)
Support schedule here:
http://www.mozilla.com/en-US/firefox/all-older.html
"Firefox 3.0.x will be maintained with security and stability updates until January 2010. All users are strongly encouraged to upgrade to Firefox 3.5."
I would DEFINITELY upgrade to Firefox 3.5. Then you can explore all of the cool stuff going on with HTML5.
Here are just a few of the HTML5 sites & demos I discovered. Some of the videos use OGG & some use H.264, so may also want to have Chrome or Safari on hand.
HTML5 WEBSITES & DEMOS
http://www.chromeexperiments.com/
http://www.canvasdemos.com/
http://html5gallery.com/
http://html5demos.com/
http://www.youtube.com/html5
http://demo.sproutcore.com/video/
http://www.rgraph.net/
http://tinyvid.tv/
http://oggtv.com/
WEB APP DEVELOPMENT
https://developer.mozilla.org/en/Canvas_tutorial
http://www.youtube.com/watch?v=siOHh0uzcuY&NR=1
http://www.brucelawson.co.uk/2009/future-of-web-design-glasgow/
http://my.opera.com/ODIN/blog/2009/10/05/future-of-web-apps-london-html5
Microsoft may have kept some things secret, so they are waiting for it to come out before they say, yes, it uses everything in Windows 7
Steam managed to do it without much trouble for example.
I like a separate button for each function. The "Simplified" taskbar is why I left IE 8.
an in fact chrome is very much smooth, fast an simple.
Sound like Google chrome advertising,
an in fact chrome is very much smooth, fast an simple.
yeah and so much naked .
You can get it for 3.5 at http://www.getpersonas.com/en-US/
This kind of statement worries the hell out of most add-ons developers. As someone who has spent 4.5 years developing a major Firefox extension containing more than 250K lines of source code, to hear Shaver say that they plan to simply "drop" a core framework that thousands of developers are currently relying on in the space of a 12-month window, its infuriating actually.
Such a fundamental developer framework needs to be phased out over a period of years, not months, and only if the replacement can do 100% of the job as the original. A lot of extensions (like Firebug and many others) are incredibly complex and "hard core". Many are just as dense and complex as the Firefox, and sometimes more so, often using the same documented and undocumented, frozen and unfrozen APIs and features as Firefox.
I would implore Mozilla to move more slowly with decisions that affect its developer community. After all, this is probably their greatest asset. As a seasoned add-ons developer, I have witnessed a fair amount of "disregard" for the needs and concerns of the developer community. How about a little R-E-S-P-E-C-T for the hard work and dedication of the development community you once worked so hard to nurture? (and a little less "me-too" stuff regarding Chrome - its starting to give us whiplash and no-one I talk to gives a hoot about Chrome anyway).
- by thejackal007 November 9, 2009 10:35 AM PST
- I like what I'm seeing for the most part but I am worried about one change coming up in Firefox 4.0. In the description for each tab getting its own process (and being able to take advantage of multiple cores), will this be slower than it is currently on 3.5 for single-core computers? I might still be in the minority but I'm using a single core Pentium IV and worry that things might be slower than they are now if this multiple core change happens.
- Like this Reply to this comment
-
-
- by espatross November 10, 2009 8:14 PM PST
- @ thejackal007- I don't imagine this should be much a worry. After all, a single processor can still run multiple threads if the programmer knows what they're doing.Even if they can't break up the processes like that for some sort of bizarre reason, the slow down would be minimal anyways because it would simply be running an extra line of code here or there that doesn't do anything. I think for most, the benefit will be considerable, and the damages done to those whom aren't able to take advantage of it should be practically nothing.
- Like this
-
Showing 1 of 2 pages (37 Comments)