Mozilla

mozilla developer preview 4 ready for testing

Note: this is a re-post of the entry in the Mozilla Project Development Weblog. There’s some juicy stuff in here for Web Developers that need testing. In particular, this is the first build with the CSS history changes.

As part of our ongoing platform development work, we’re happy to announce the fourth pre-release of the Gecko 1.9.3 platform. Gecko 1.9.3 will form the core of Firefox and other Mozilla project releases.

It’s available for download on Mac, Windows or Linux.

Mozilla expects to release a Developer Preview every 2-3 weeks. If you’ve been running a previous release, you will be automatically updated to the latest version when it is released.

This preview release contains a lot of interesting stuff that’s worth pointing out, and contains many things that were also in previous releases. Here are the things of note in this release:

User Interface Changes

  • Open tabs that match searches in the Awesomebar now show up as “Switch to Tab.”
  • This is the first preview release to contain resizable text areas by default.

Web Developer Changes

  • This is the first preview release to contain changes to CSS :visited that prevent a large class of history sniffing attacks. You can find more information about the details of why this change is important over on the hacks post on the topic and on the Mozilla Security Weblog. Note that this change is likely to break some web sites and requires early testing – please test if you can.
  • SVG Attributes which are mapped to CSS properties can now be animated with SMIL. See the bug or a demo.

Plugins

  • Out of process plugins support for Windows and Linux continues to improve. This release contains many bug fixes vs. our previous developer preview releases. (In fact, it’s good enough that we’ve ported this code back to the 3.6 branch and have pushed that to beta for a later 3.6.x release.)
  • This is the first release that contains support for out of process plugins for the Mac. If you are running OSX 10.6 and you’re running the latest Flash beta, Flash should run out of process

Performance

  • One area where people complained about performance was restart performance when applying an update. It turns out that a lot of what made that experience poor wasn’t startup time, it was browser shutdown time. We’ve made a fix since the last preview release that made a whopping 97% improvement in shutdown time. (That’s not a typo, it’s basically free now.)
  • Our work to reduce the amount of I/O on the main thread continues unabated. This preview release will feel much snappier than previous snapshots, and feel much faster than Firefox 3.6.
  • We continue to add hardware acceleration support. If you’re on Windows and you’ve got decent OpenGL 2 drivers, open video will use hardware to scale the video when you’re in full screen mode. For large HD videos this can make a huge difference in the smoothness of the experience and how much power + CPU are used. We’ll be adding OSX and Linux support at some point in the future as well, but we’re starting with Windows.
  • We continue to make improvements and bug fixes to our support for Direct2D. (Not enabled by default. If you want to turn it on see Bas’ post.) If you’re running Alpha 4 on Windows Vista or Windows 7, and you’ve turned on D2D, try running this stress test example in Alpha 4 vs. Firefox 3.6. The difference is pretty amazing. You can also see what this looks like compared to other browsers in this this video. (Thanks to Hans Schmucker for the video and demo.)

Platform

  • JS-ctypes, our new easy-to-use system for extension authors who want to call into native code now has support for complex types: structures, pointers, and arrays. For more information on this, and how easy it can make calling into native code from JavaScript, see Dan Witte’s post.
  • Mozilla is now sporting an infallible allocator. What is this odd-sounding thing, you ask? It’s basically an allocator that when memory can’t be allocated it aborts instead of returning NULL. This reduces the surface area for an entire class of security bugs related to checking NULL pointers, and also allows us to vastly simplify a huge amount of Gecko’s source code.

8 comments

Comments are now closed.

  1. sombriks wrote on April 14th, 2010 at 16:01:

    i’ve tested the linux version.

    dude, the webgl examples are all working now, thanks a lot mozilla team!

    also the v8 benchmark is just 2x faster than before.

    one question: will ctypes replace xpcom? at the first moment sounds quite nice, :) but i’m not a mozilla guru to guess correctly.

    other: when will be possible to have a firefox “in a system wide way”?

    see, keep almost all libs inside a folder makes my slackware like a windows box. will some day we have firefox-bin under /usr/bin and libs under /usr/libs?

  2. Christopher Blizzard wrote on April 14th, 2010 at 17:49:

    The js-cytypes stuff doesn’t replace XPCOM. It does make a lot of things much easier when trying to interact between JS and native code, however. Much, much easier.

    Yeah, we’re cranking on a lot of JS performance as well. V8 got a lot better, and we’ve got some other improvements in the pipeline esp. for a lot of graphics stuff. A lot of that applies on Windows first, but it’s a good model for a place to start. Eventually we’ll have OpenGL on Linux as well, even outside of WebGL.

    Re: the system wide library, that’s really up to the individual packagers for Linux.

  3. Tiago Sá wrote on April 15th, 2010 at 10:16:

    Resizeable textareas by default?! Cool! I can finally uninstall the addon I had for that :) Good going!

  4. Neil | California Web Design wrote on April 15th, 2010 at 11:18:

    Ready to test it out will let you know soon

    FireFox Rocks

  5. Daniel H. wrote on April 18th, 2010 at 12:09:

    When is Firefox 3.6 with out-of-process plug-ins supposed to be released?

    1. Christopher Blizzard wrote on April 18th, 2010 at 18:43:

      It’s in beta now!

      http://www.mozilla.com/en-US/firefox/lorentz/

      Feel free to try it out.

  6. Style Thing wrote on April 22nd, 2010 at 06:36:

    Due to :visited changes, my stylish theme is not fully working now :(
    I use the change of the background and rounded corners with :visited, and now it all does not work

    Link to userstyles.org:
    http://userstyles.org/styles/11306

  7. YuriKolovsky wrote on November 11th, 2010 at 08:19:

    in firefox 4, remove cross-domain :visited links, and a button to enable them again, and consider replying to “some” comments.

Comments are closed for this article.