1. Mozilla
  2. Firefox
  3. Release notes for developers
  4. Firefox 15

Firefox 15 release notes for developers

Firefox 15 shipped on August 28, 2012. This article lists key changes that are useful for not only Web developers to know about, but also Firefox and Gecko developers as well as add-on developers.

Changes for Web developers

HTML

  • The size attribute of the <font> element is now handled according to the HTML5 specification. It means that all integer values greater than 10 or less than -10 are now considered equivalent to 10 and -10, respectively.
  • Support for font-weight and point-size attributes on the <font> element has been removed; these were non-standard and Gecko was the only engine that supported them.
  • The Opus codec is now supported for audio in Ogg containers for the HTML <audio> and <video> elements.
  • The <source> element now supports the media attribute.
  • The <audio> and <video> elements now support the played attribute, which provides a TimeRanges object listing the time ranges of the media that have been played back so far.

CSS

  • The font-feature-settings property has been updated to the latest syntax: font-feature-settings: "lnum" 1;
  • The CSS text-transform property has been extended to correctly handle Unicode ligature characters (like fi).
  • The CSS word-break property has been implemented.
  • The border-image property has been updated to match the latest Specification and properties have been unprefixed. (bug 713643)
  • The skew() transform function dropped in Firefox 14 has been restored due to existing site compatibility. Authors are however, advised to use skewX() and skewY() functions instead.
  • The value plaintext of CSS unicode-bidi property now applies to inline elements too. (Firefox bug 746987).

DOM

  • The DOM Events Level 3 methods KeyboardEvent.getModifierState() and MouseEvent.getModifierState(), which let you query the state of modifier keys, like Ctrl or Shift, have been implemented (bugs 630811 and 731878). But the behavior conforms to the latest D3E draft. So, some modifier key names are different from IE (Firefox bug 769190).
  • On mouse events, support for querying the state of the mouse buttons using the MouseEvent.buttons attribute, has been implemented.
  • On keyboard events, support for querying the key location (standard, left or right of modifier key, in the Numpad) using the KeyboardEvent.location attribute, has been implemented (Firefox bug 166240).
  • KeyboardEvent.keycode result has been computed from better rules which were almost same on Windows/Linux/Mac. And now they are available on some keyboard layouts which are not ASCII capable layouts on Linux and Mac, such as Arabic, Cyrillic, Thai and so on. See the document for virtual key codes.
  • The range.detach() method has been transformed in a no-op and will probably be removed in the future.
  • The method HTMLVideoElement.mozHasAudio() has been implemented. It indicates if there is an audio track associated to a given video element. (bug 480376)
  • The Performance API has a new method, now(), supporting high resolution timers of type DOMHighResTimeStamp. (bug 539095).
  • The WebSMS API has been updated and now supports a read attribute indicating whether an SMS text message is read or unread.
  • The FileHandle API has been implemented.
  • The Blob constructor now takes ArrayBufferView as a member of blobParts parameter in addition to ArrayBuffer. (bug 752402)
  • The DeviceLightEvent specified in the Ambient Light Events Working Draft has been implemented.
  • The DeviceProximityEvent and UserProximityEvent Proximity Events have been implemented.
  • The File lastModifiedDate property has been implemented. (Firefox bug 673586)

JavaScript

WebGL

  • Support for the WEBGL_compressed_texture_s3tc extension has been added. Compressed textures reduce the amount of memory needed to store a texture on the GPU, allowing for higher resolution textures or more of the same resolution textures.

MathML

SVG

Network

  • Support for the SPDY v3 protocol has landed. It is disabled by default and can be enabled by setting the preference network.http.spdy.enabled.v3 to true. (bug 737470)

Changes for add-on and Mozilla developers

Interface changes

nsIDOMWindowUtils

aModifiers of sendMouseEvent(), sendTouchEvent(), sendMouseEventToWindow(), sendMouseScrollEvent() and sendKeyEvent() supports all modifier keys which are supported by KeyboardEvent.getModifierState(). Use MODIFIER_* values. And now the 5th parameter of sendKeyEvent() is changed from boolean to unsigned long. For backward compatibility, if caller passes true or false to it, the behavior isn't changed. This change allows callers to specify the key's location.

nsIBrowserHistory

The hidePage() method was never implemented, and has been removed entirely in this release. The addPageWithDetails() method has also been removed as part of the ongoing work to make all 'Places APIs' asynchronous; use mozIAsyncHistory.updatePlaces() instead. Also, the count attribute was removed; it had not returned an actual count in some time (instead, it was indicating whether or not any entries existed). You can use nsINavHistoryService.hasHistoryEntries instead.

nsIDOMUtils

The nsIDOMUtils.parseStyleSheet() method has been added and allows the (re-)parsing of Cascading Style Sheets.

nsIINIParserWriter

The nsIINIParserWriter.writeFile() method now accepts a flags property. This currently offers only one option: you can now tell it to write the file in UTF-16 format instead of UTF-8, for better compatibility with Windows and certain installers.

New interfaces

nsISpeculativeConnect

Provides a way to hint to the networking layer that you are likely to ask to open a connection to a given URI sometime in the near future. This lets the network layer begin the sometimes high-latency process of opening a new network connection ahead of time.

Removed interfaces

The following interfaces have been removed:

  • nsIGlobalHistory

Help improve MDN

Learn how to contribute

This page was last modified on by MDN contributors.

View this page on GitHub • Report a problem with this content