Firefox 11 技術文件
Firefox 11 shipped on March 13, 2012. This article provides information about the new features and key bugs fixed in this release, as well as links to more detailed documentation for both web developers and add-on developers.
element.outerHTMLproperty is now supported on HTML elements.
XMLHttpRequestsupports HTML parsing.
- Removed support for using the
withCredentialsattributes when performing synchronous requests. Attempting to do so throws an
NS_ERROR_DOM_INVALID_ACCESS_ERRexception. This change has been proposed to the W3C for standardization.
- The new
window.navigator.mozVibrate()method lets you vibrate the device where supported; this is implemented as
Appsobject you can use to install and manage open web applications.
MozBeforePaintevents are no longer fired.
mozRequestAnimationFrame()consumers who used these should pass a callback function instead.
- Support for canceling animation frame requests has been added;
window.mozRequestAnimationFrame()now returns a request ID value, which you can pass to
window.mozCancelAnimationFrame()to cancel the request.
Event, HTML events,
MouseEvent) introduced in DOM4 specifications are now supported.
Battery APIis now enabled by default.
- Support for the
HTMLMediaElementhas been added.
document.mozCancelFullScreen()now restores the previously full-screen element if some other element was in full-screen mode when the current element's
element.mozRequestFullScreen()method was called.
window.mozRequestAnimationFrame()method no longer supports a no-argument form. This form was not used much and is unlikely to become part of the standard.
- SVG-as-an-image can now be drawn into a canvas without tainting the canvas.
- The non-standard
countryCodeproperty of the
GeoPositionAddressinterface has been removed; see
- Server-sent events now support CORS.
- In the past, when the user followed a link, the values set on the
window.navigatorobject were retained by the new page. Now a new
navigatorobject is created for the new page. This makes Firefox behave like all other browsers.
SVGSVGElementDOM interface now support the
- WebSocket API now supports binary messages (see bug 676439).
- Both the protocol and the API has been updated to the latest draft of the specification and the API has been unprefixed (see bug 666349 and bug 695635).
- Previously, messages sent and received using WebSockets in Firefox were limited to 16 MB in size; they may now be up to 2 GB (although memory capacity limitations may prevent them from being that large, Firefox supports it).
- The change in Firefox 8 that removed support for double quote characters as delimiters for RFC 2231 and RFC 5987 has been reverted, as this broke some sites, including Outlook Web Access.
- The user agent string in HTTP headers now includes an identifier that lets the server know if the Firefox accessing it is a phone or a tablet.
readInputStreamToString()has a new, optional, parameter to configure the character set interpretation while reading the input stream.
mozIAsyncHistoryinterface has a new method
mozIAsyncHistory.isURIVisited()to check if a URI has been visited.
- A new interface
mozIVisitStatusCallbackhas been added to provide callback handling functionality for
nsIMacDockSupportinterface now supports adding a text badge to the application's icon in the Dock using its new
- In the
nsINavHistoryResultObserverinterface, you now need to implement
nsINavHistoryResultObserver.containerStateChanged()instead of the obsolete
The following interfaces were implementation details that are no longer needed:
omni.jarfile is now called
- Specifies the delay, in milliseconds, between the mouse cursor beginning to hover and the display of a tooltip.
--enable-tracejitbuild option has been removed.
- Add-ons that have not been updated in a long time are no longer assumed to be compatible by default; this is currently add-ons that indicate a