Please note, this is a STATIC archive of website developer.mozilla.org from 03 Nov 2016, cach3.com does not collect or store any user information, there is no "phishing" involved.

I volontari di MDN non hanno ancora tradotto questo articolo in Italiano. Registrati per tradurlo tu.

Firefox 36 was released on February 24th, 2015. This article lists key changes that are useful not only for web developers, but also Firefox and Gecko developers as well as add-on developers.
 

Changes for Web developers

Developer Tools

Highlights:

All devtools bugs fixed between Firefox 35 and Firefox 36.

CSS

HTML

  • Support for <meta name="referrer"> has been added (bug 704320).
  • In Firefox, <input> filters specified in the accept attribute will always be selected by default, unless there is a unknown value, that is an unknown mime type or badly formatted value in the accept attribute. Previously specified filters were only selected by default for image/*,video/* and audio/* values (bug 826185).

JavaScript

Interfaces/APIs/DOM

 

MathML

No change.

SVG

No change.

Audio/Video

No change.

Networking

  • Support for SPDY/3 has been removed; support for SPDY/3.1 is still available (bug 1097944).

Security

  • RC4 is now considered as insecure and all UI indicators will react as such; SSLv3 has been disabled by default in Firefox 34, but the UI has been changed to help the user better understand what is happening (bug 1093595).
  • Also, RC4 is no longer offered in the initial handshake of TLS (bug 1088915).
  • The form-action directive of CSP 1.1 is now supported (bug 529697).
  • In the preferences of Firefox, The Do not track selection widget is again an on/off switch (bug 1071747).

Changes for add-on and Mozilla developers

Add-on SDK

Highlights

var { require } = Cu.import("resource://gre/modules/commonjs/toolkit/require.js", {});

Details

Github commits made between Firefox 35 and Firefox 36.

JavaScript code modules

Interfaces

nsIContentPolicy

New constants have been added to nsIContentPolicy to allow Gecko internals and add-on code to better differentiate different types of requests. These are:

TYPE_FETCH
Indicates a content load request initiated by the GlobalFetch.fetch() method.
TYPE_IMAGESET
Indicates a request to load an <img> (with the srcset attribute or <picture> element.

XUL

No change.

Other

See also

Older versions

Tag del documento e collaboratori

Tag: 
 Hanno collaborato alla realizzazione di questa pagina: Sebastianz, kohei.yoshino, serv-inc, Sheppy, teoli, chrisdavidmills, evold, kmaglione, phistuck, MagnetMan, Havvy, Vento, fscholz, fmarier, arai, wbamberg, ziyunfei, myakura
 Ultima modifica di: Sebastianz,