MDN wants to learn about developers like you:

На этой странице возникли скриптовые ошибки. Хотя они адресуются редакторам сайта, вы можете просмотреть частичное содержимое ниже.

Наши волонтёры ещё не перевели данную статью на Русский. Присоединяйтесь к нам и помогите сделать эту работу!
Вы можете также прочитать эту статью на English (US).

Firefox 6, based on Gecko 6.0, was released on August 16, 2011. This article provides links to information about the changes that affect developers in this release.

Changes for web developers


  • The HTML5 <progress> element, which lets you create a progress bar, is now supported.
  • The parsing of the HTML5 <track> element, which specifies text tracks for media elements, is now supported. This element should appear in the DOM now, though its behavior is still not implemented.
  • The <iframe> element is now clipped correctly by its container when the container's corners have been rounded using the border-radius property.
  • <form> elements' text <input> fields no longer support the XUL maxwidth property; this was never intentional, and is in violation of the HTML specification. You should instead use the size attribute to set the maximum width of input fields.
  • The <canvas> CanvasRenderingContext2d properties fillStyle and strokeStyle used to ignore garbage included after a valid color definition; now this is correctly treated as an error. For example, "red blue" as a color used to be treated as "red", when it should have been ignored.
  • The width and height of <canvas> elements can now properly be set to 0px; previously, these were getting arbitrarily set to 300px when you tried to do that.
  • Support for the HTML custom data attributes (data-*) has been added. The DOM element.dataset property allows to access them.
  • When a <textarea> element receives focus, the text insertion point is now placed, by default, at the beginning of the text rather than at the end. This makes Firefox's behavior consistent with other browsers.


This new property lets you set the color used by text decorations, such as underlines, overlines, and strikethroughs.
This new property lets you set the kind of text decorations added to an element.
This new property lets you set the style of text decorations, such as underlines, overlines, and strikethroughs. Styles include single-strokes, double strokes, wavy lines, dotted lines, and so forth.
This new property lets you control how hyphenation of words during line wrapping is handled.
A new (currently Mozilla-specific) property which lets you control the vertical or horizontal orientation of certain elements (particularly <progress>).
A Mozilla-specific pseudo-element that lets you style the area of an <progress> element representing the completed portion of a task.

Other changes

  • The @-moz-document property has a new regexp() function, which lets you match the document's URL to a regular expression.
  • The azimuth CSS property is no longer supported, as we have removed what little code we had for the aural media group. It was never significantly implemented, so it made more sense to remove the crufty implementation for the time being rather than try to patch it up.
  • In the past, the :hover pseudoclass was not applied to class selectors when in quirks mode; for example, .someclass:hover did not work. This quirk has been removed.
  • The :indeterminate pseudo-class can be applied to <progress> elements. This is non-standard, but we hope it will be adopted by other browsers, because it will be useful.
  • The -moz-win-exclude-glass value has been added to the -moz-appearance CSS property in order to exclude opaque regions in Aero Glass glaze effects on Windows systems.
  • bug 658949 changed how the hash (#) symbol is treated in data URIs which may break CSS stylesheets which contain such a symbol if it is not escaped.


Using media queries from code
You can now test the result of a media query string programmatically using the window.matchMedia() method and the MediaQueryList interface.
Touch events
Firefox 6 adds support for W3C standard touch events; these make it easy to interpret one or more touches at a time on touch-sensitive surfaces such as touch screens and trackpads.
Server-sent events
Server-sent events make it possible for a web application to ask a server to send events just like any locally-created DOM event.
  • navigator.securityPolicy, which has returned an empty string for a long time, has been removed outright.
  • BlobBuilder is now implemented, although for now it's prefixed (so you need to use MozBlobBuilder).
  • The document.height and document.width have been removed. bug 585877
  • The DocumentType object's entities and notations properties, which were never implemented and always returned null, have been removed, since they've been removed from the specification anyway.
  • The DOMConfiguration interface and the document.domConfig property that used it have both been removed; they were never supported and have since been removed from the DOM specification.
  • The hashchange event now correctly includes the newURL and oldURL fields.
  • The FileReader interface's abort() method now throws an exception when used if no file read is in progress.
  • The window.postMessage() method now uses the structured clone algorithm to let you pass JavaScript objects instead of just strings from one window to another.
  • The window.history API now uses the structured clone algorithm to serialize the objects you pass to the pushState() and replaceState() methods; this lets you use more complex objects (including those that contain cyclic graphs of references).
  • You can now detect when printing has been initiated and has completed by listening for the new beforeprint and afterprint events.
  • The document.strictErrorChecking property has been removed, since it was never implemented and was removed from the DOM specification.
  • The standard event.defaultPrevented property is now supported; you should use this instead of the non-standard getPreventDefault() method to detect whether or not event.preventDefault() was called on the event.
  • The property is now properly read only.
  • DOM views, which we never documented, have been removed. This was a bit of implementation detail that was unnecessarily complicating things, so we got rid of it. If you notice this change, you're probably doing something wrong.
  • The EventTarget function addEventListener()'s useCapture parameter is now optional, as it is in WebKit (and as per the latest version of the specification).
  • The mozResponseArrayBuffer property of the XMLHttpRequest object has been replaced with the responseType and response properties.
  • The element.dataset property has been added to the HTMLElement interface allowing access to the data-* global attributes of an element.
  • The CustomEvent interface has been implemented. (see bug 427537)
  • For security reasons, data: and javascript: URIs no longer inherit the security context of the current page when the user enters them in the location bar; instead, a new, empty, security context is created. This means that script loaded by entering javascript: URIs in the location bar no longer has access to DOM methods and the like, for example. These URIs continue to work as before when used by script, however.


  • In the past, it was possible to use the new operator on several built-in functions (eval, parseInt, Date.parse...) that should not have allowed it, according to the specification. This behavior is no longer supported. Using the new operator in this way was never officially supported and was not widely done, so it's unlikely that this change affects you.
  • ECMAScript 2015 WeakMaps have been added as a prototype implementation.


  • The pathLength attribute is now supported.
  • SVG patterns, gradients, and filters now work correctly when loaded from data: URLs.


  • The implementation of <mstyle> has been corrected.

Accessibility (ARIA)

  • A state change event is now correctly sent when the value of aria-busy changes.
  • An attribute change event is now correctly sent when aria-sort occurs.


WebSockets was updated to protocol version 07 for Firefox 6. In addition, the global WebSocket object has been renamed to MozWebSocket to prevent it from incorrectly being used to detect the availability of unprefixed WebSockets.
  • Parsing of the Content-Disposition header has been fixed to properly interpret backslash-escaped ASCII characters as just that character itself. Previously it was incorrectly replacing that character with an underscore ("_").
  • The value of the path field on Set-Cookie headers is now interpreted correctly when quotes are used; previously, they were being treated as part of the path string instead of as delimiters. This change may affect compatibility with some web sites, so authors should check their code.
  • The Upgrade request header is now supported; you can request an upgrade of an HTTP channel to another protocol by calling nsIHttpChannelInternal.HTTPUpgrade().

Other changes

  • Support for microsummaries has been removed; these were never widely used, were not very discoverable, and continuing to support them was making improvements to the Places (bookmark and history) architecture difficult.
  • WebGL now supports the OES_texture_float extension.
  • The new Scratchpad tool provides a handy place to experiment with JavaScript code.
  • The console.trace() method has been added to the ConsoleAPI (see {{ bug }}).

Changes for Mozilla and add-on developers

For an overview of the changes you may need to make in order to make your add-on compatible with Firefox 6, see Updating add-ons for Firefox 6.

Note: Firefox 6 requires that binary components be recompiled, as do all major releases of Firefox. See Binary Interfaces for details.

JavaScript code modules


  • The openSafeFileOutputStream() method now opens files with the DEFER_OPEN behavior flag instead of attempting to open them immediately.


  • The new importRelative() method lets you load one JavaScript code module from a path relative to the path of another JavaScript code module. This makes it easier to build modules that depend on each other.


Using the DOM from chrome

Using the DOM File API in chrome code
Although you've always been able to use the DOM File API from chrome code, the File constructor now supports specifying a local pathname string when used from chrome. In addition, you can also specify the file to access using the DOM File API using an nsIFile object.

Interface changes

New interfaces

A new service that lets you access the favicon service asynchronously.
Details forthcoming.
Details forthcoming.
Details forthcoming.
The callback interface for handling HTTP upgrade requests via the nsIHttpChannelInternal.HTTPUpgrade() method.
A container for objects that have been serialized using the structured clone algorithm.
Implements telemetry support to allow recording of telemetry data to be used to present histograms for performance tracking purposes. See bug 649502 and bug 585196.
See bug 576006.
See bug 640003.
See bug 640003.

Removed interfaces

The following interfaces were implementation details that are no longer needed:

Other changes

Using preferences from application code
A new static API is available for easily accessing preferences; this is only available to application code and can't be used by add-ons.

See also

Метки документа и участники

 Обновлялась последний раз: Sebastianz,