Mozilla

We’re happy to announce the availability of Aurora 10.
(Download and Test Aurora 10)

In additional to the normal improvements that you’ve come to expect like performance, security and bug fixes, Aurora 10 focuses in HTML5 enhancements.

New additions

Developer Tools

Aurora 10 also implements incremental enhancements like IndexedDB setVersion API changes. Ongoing detailed attention to evolving specifications help to keep Firefox at the front of the Web revolution. (Read more about IndexedDB on MDN.)

DOM

  • We now fire a “load” event on stylesheet linking when the sheet load finishes or “error” if the load fails.
  • We turn the POSTDATA prompt into an information page (when navigating in session history).
  • We only forward event attributes on body/frameset to the window if we also forward the corresponding on* property.
  • We no longer allow more than one call to window.open() when we allow popups.
  • We fixed a bug where a success callback never fired when a position update is triggered after getCurrentPosition().
  • We removed replaceWholeText().
  • We fixed an error with createPattern(zero-size canvas).
  • We now handle putImageData(nonfinite) correctly.
  • We now throw INVALID_STATE_ERR when dispatching uninitialized events.
  • We’ve made Document.documentURI readonly.
  • We fixed document.importNode to comply with optional argument omitted.

Web workers

  • We now allow data URLs.
  • We implemented event.stopImmediatePropagation in workers.
  • We made XHR2 response/responseType work in Web Workers.

Graphics

  • We implement the WebGL OES_standard_derivatives extension.
  • We implement minimal-capabilities WebGL mode.

JavaScript

  • The function caller property no longer skips over eval frames.
  • We fixed E4X syntax so that it is not accepted in ES5 strict mode.
  • weakmap.set no longer returns itself instead of undefined.
  • We implemented the battery API.

Offline: IndexedDB enhancements

  • IndexedDB setVersion API changes
  • Added support for IDBObjectStore/IDBIndex.count
  • Various methods accept both keys and KeyRanges.
  • Added support for IDBCursor.advance.
  • Implemented deleteDatabase.
  • objectStoreNames are no longer updated on closed databases when another connection adds or removes object stores
  • IDBObjectStore.delete and IDBCursor.delete now return undefined.
  • No longer throws an error if there are unknown properties in the options objects to createObjectStore/createIndex.
  • We now the errorCode to “ABORT_ERR” for all pending requests when IDBTransaction.abort() is called.
  • Fixed the sort order for indexes.

Layout

  • We have updated the current rule for handling malformed media queries.
  • We now support the HTML5 <bdi> element and CSS property unicode-bidi: isolate.
  • The CSS3 implementation now supports unicode-bidi: plaintext.

Media

  • Implemented Document.mozFullScreenEnabled.
  • Enabled the DOM full-screen API on desktop Firefox by default.

19 comments

Comments are now closed.

  1. Caspy7 wrote on November 11th, 2011 at 23:48:

    In the New additions section I’m seeing “HTML5 Visibility API” and “Visibility API”. Is this an accidental dup or are these things different? (If so I’m curious how.)

  2. redpanda wrote on November 12th, 2011 at 00:06:

    can’t wait for it on the debian repo, bring it on :)

  3. A.I. wrote on November 12th, 2011 at 03:43:

    Page Visibility API support is awesome. Maybe my this API wrapper will be useful for someone (to use move high-level function or clear code from vendor prefixes) https://github.com/evilmartians/visibility.js

  4. Benoit Jacob wrote on November 12th, 2011 at 09:24:

    Everytime a hacks.mozilla.org article is tagged WebGL, it appears on planet-webgl.org. That’s why the WebGL category must be used sparingly, only for articles that are predominantly about WebGL. We’re currently the only browser vendor to be spamming planet-webgl in this way. I’ve tried a few times emailing people when this has happened in the past, but nothing has changed. I’m going to try to find planet-webgl admins and ask them to remove the hacks.mozilla.org WebGL aggregation. This is too bad, as there also were actual WebGL articules on hacks.m.o that were useful to aggregate on planet-webgl.

    1. pd wrote on November 12th, 2011 at 22:20:

      Spam? Rubbish! That’s a really bizarre analysis. If I cared about WebGL and as a planet webgl readers, the first a foremost thing I would want to know is updates on how browsers are implementing it.

      hack.mozilla.org – of all the many aggregated Mozilla sources – is about the only place, outside of the practically-unreadable bugzilla, that presents clear lists of technically termed features that are implemented by Mozilla. Why should WebGL users have to also be planet mozilla users in order to find out a broad understanding of what is happening with Mozilla’s WebGL effort from the varius individuals who may, or may not, choose to write an article about the topic?

  5. thinsoldier wrote on November 12th, 2011 at 11:24:

    I know this isn’t the right place for this but I’ve tried the help center and irc channels and haven’t received any help yet.

    I have a major problem with firefox on my mac that has existed in the release version since 5 and in the nightly since a few weeks ago but NEVER in Aurora and I’ve been using aurora since Firefox 5 was released.

    The problem is any domain defined in my hosts file (for local development work) does not load in Firefox but does load in Aurora and does not load in Beta or Nightly.

    Why would that happen? It makes no sense for months of Aurora releases to not have a bug yet the bug exists in every new Firefox.

  6. Benoit Jacob wrote on November 12th, 2011 at 11:29:

    @thinsoldier: the right place for that is to file a bug at bugzilla.mozilla.org. probably Firefox->General unless you can find a more appropriate component (IRC can help with that).

  7. Ken Saunders wrote on November 12th, 2011 at 18:26:

    How do enable and access the new developer tools?

    1. pd wrote on November 12th, 2011 at 22:21:

      Tools -> Web Developer menu

  8. Kevin Dangoor wrote on November 12th, 2011 at 21:52:

    Ken: the new developer tools are available under the Web Developer menu (Tools/Web Developer on the Mac). You can also select Inspect Element from the context menu on any part of the page.

  9. Jerry wrote on November 13th, 2011 at 09:05:

    Great! Salute

  10. Ken Saunders wrote on November 13th, 2011 at 12:17:

    I forgot that the (Inspector) toolbar is dark and at the bottom. I didn’t notice it right away because my add-on bar is dark.

  11. Jason wrote on November 14th, 2011 at 10:34:

    So I’m trying to figure out these built-in developer tools. Am I right that the code-editor it only allows for changing of css properties and existing html attributes, but doesn’t allow for other changing of the html tag and it’s attributes or editing the text, at the moment?

    And will there be an effort to put Web Console, Inspector, Scratchpad and Error Console together into one cohesive frame, sort of like how we get their equivalents them together in Firebug?

  12. Kevin Dangoor wrote on November 14th, 2011 at 11:03:

    @Jason: You’re correct about the current editing you can do.

    We are planning to have a combined view, and a way to put that combined view into a separate window. So far, I actually like the ability to bring up just the views I want for the problem at hand, but there are many good reasons to want a window with easy access to everything.

    That said, we don’t have any plans to integrate the Error Console as it stands. The Web Console is the future there. Is there something you use the Error Console for?

    1. Jason wrote on November 14th, 2011 at 11:43:

      Actually I didn’t realize the web console has javascript errors and stuff.

  13. Rene wrote on November 16th, 2011 at 05:24:

    Some properties seem not to work with/without vendor prefix:
    perspective
    perspective-origin

    Is it just me or can someone confirm?

    Thx.

    1. Jason wrote on November 16th, 2011 at 10:18:

      I know that perspective requires units on the number.

      1. Rene wrote on November 16th, 2011 at 10:36:

        Thx, that’s it.

        However the specs changed: http://www.w3.org/TR/css3-3d-transforms/#perspective

        Values for the perspective property are now none or , not anymore.

  14. Rene wrote on November 16th, 2011 at 10:37:

    Oops: number not length anymore.

Comments are closed for this article.