Firefox 42 for developers

Cette traduction est incomplète. Aidez à traduire cet article depuis l'anglais.

Install Firefox Developer Edition

Firefox 42, based on Gecko 42, will ship in November 2015. This article provides information about the changes in this release that will affect developers. Nightly builds of what will become Firefox 42 are currently available on the Beta channel.

Note: Items listed here are tentatively slated for Firefox 42; however, they may be held for a future release if testing shows they're not ready by the time Firefox 42 is due to ship. Please keep an eye on this page to stay up to date on the plans for Firefox 42.

Changes for Web developers

Developer Tools

Highlights:

All devtools bugs fixed between Firefox 41 and Firefox 42.

CSS

HTML

JavaScript

Interfaces/APIs/DOM

DOM & HTML DOM

Service Workers

Web Animations API

Our experimental implementation of Web Animations API have been extended to support:

Web Components

Our experimental implementation of the Shadow DOM has been modified:

WebGL

WebRTC

New APIs

  • The ImageBitmap interface and the createImageBitmap() method have been implemented. They are available on regular window scripts and in Web workers and allow efficient posting of images between window and worker contexts (bug 1044102).

Miscellaneous

MathML

No change.

SVG

No change.

Audio/Video

No change.

HTTP

  • Firefox 41 and earlier versions were incorrectly accepting undefined or invalid pseudo-header fields in HTTP/2 responses. This is now fixed and the only pseudo-header field accepted from Firefox 42 is the :status as per the specification. Response headers containing arbitrary fields are considered malformed.

Networking

Security

  • EV certificates with a validity greater than 39 months are now considered and handled as DV certificates (bug 1145679).

Changes for add-on and Mozilla developers

Interfaces

nsIContentPolicy

  • The TYPE_EMBED constant has been added to nsIContentPolicy to allow Gecko internals and add-on code to better differentiate different types of requests. Previously, TYPE_OBJECT was used for these cases (bug 1148030).
  • Similarly, the TYPE_SUBDOCUMENT constants has been split into TYPE_FRAME and TYPE_IFRAME (bug 1148044).

XUL

No change.

JavaScript code modules

No change.

XPCOM

No change.

Other

No change.

See also

Older versions

Étiquettes et contributeurs liés au document

 Contributeurs à cette page : syoichi
 Dernière mise à jour par : syoichi,