Firefox 35

by



Jan 26, 2015 Firefox Release January 26, 2015 Version 35.0.1, first offered to Release channel users on January 26, 2015 We'd also like to extend a special thank you to all of the new Mozillians who contributed to this release of Firefox! Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. Chocolatey integrates w/SCCM, Puppet, Chef, etc. Chocolatey is trusted by businesses to manage software deployments.

Firefox 35 was released on January 13th, 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: Alarm clock app for mac free download.

All devtools bugs fixed between Firefox 34 and Firefox 35.

CSS

  • The mask-type property has been activated by default (bug 1058519).
  • The filter property is now activated by default (bug 1057180).
  • The @font-face at-rule now supports WOFF2 fonts (bug 1064737).
  • The symbols() functional notation is now supported (bug 966168).
  • The CSS Font Loading API has been implemented (bug 1028497).
  • Using -moz-appearance with the none value on a combobox now remove the dropdown button (bug 649849).
  • The property accessor element.style['css-property-name'] has been added to match other browsers (bug 958887).

HTML

  • The obsolete and non-conforming bottommargin, leftmargin, rightmargin and topmargin attributes of the <body> element have been activated in non-quirks mode (bug 95530).

JavaScript

  • The 'temporal dead zone' for let declarations has been implemented. In conformance with ES2015 let semantics, the following situations
    now throw errors. See also this newsgroup announcement and bug 1001090.
    • Redeclaring existing variables or arguments using let within the same scope in function bodies is now a syntax error.
    • Using a variable declared using let in function bodies before the declaration is reached and evaluated is now a runtime error.
  • ES2015 Symbols (only available in the Nightly channel) have been updated to conform with recent specification changes:
    • String(Symbol('1')) now no longer throws a TypeError; instead a string ('Symbol(1)') gets returned (bug 1058396).
  • The various TypedArray constructors now have as their [[Prototype]] a single function, denoted %TypedArray% in ES2015 (but otherwise not directly exposed). Each typed array prototype now inherits from %TypedArray%.prototype. (%TypedArray% and %TypedArray%.prototype inherit from Function.prototype and Object.prototype, respectively, so that typed array constructors and instances still have the properties found on those objects.) Typed array function properties now reside on %TypedArray%.prototype and work on any typed array. See TypedArray and bug 896116 for more information.
  • ES2015 semantics for prototype mutations using object literals have been implemented (bug 1061853).
    • Now only a single member notated as __proto__:value will mutate the [[Prototype]] in the object literal syntax.
    • Method members like __proto__() {} will not overwrite the [[Prototype]] anymore.

Interfaces/APIs/DOM

  • The NavigatorLanguage interface is now available to workers on WorkerNavigator (bug 925849).
  • The Element.closest() method returns the closest ancestor of the current element (bug 1055533).
  • Experimental support for the CanvasRenderingContext2D.filter property has been added behind the canvas.filters.enabled flag (bug 927892).
  • Our experimental implementation of Web Animations progresses with the landing of the Animation.target property. This always is behind the dom.animations-api.core.enabled pref, off by default (bug 1067701).
  • The hasAttributes() method has been moved from Node to Element as required by the spec (bug 1055773).
  • The crossOrigin reflected attribute of HTMLImageElement, HTMLLinkElement, HTMLMediaElement, HTMLScriptElement, and SVGScriptElement only accepts valid values, and ' isn't, null has to be used instead (bug 880997).
  • The Resource Timing API has been activated by default (bug 1002855).
  • To match the spec, the first argument of Selection.containsNode() cannot be null anymore (bug 1068058).
  • The new ImageCapture API has been implemented: ImageCapture.takePhoto() is available (bug 916643).
  • Non-HTTP XMLHttpRequest requests now return 200 in case of success (instead of the erroneous 0) (bug 716491).
  • XMLHttpRequest.responseURL has been adapted to the latest spec and doesn't include the fragment ('#xyz') of the URL, if relevant (bug 1073882).
  • The internal, non-standard, File.mozFullPath property is no more visible from content (bug 1048293).
  • The constructor of File has been extended to match the specification (bug 1047483).
  • An experimental implementation of AbortablePromise, a promise that can be aborted by a different entity that the one who created it, has been added. It is prefixed with Moz and controlled by the dom.abortablepromise.enabledproperty, defaulting to false (bug 1035060).
  • The non-standard Navigator.mozIsLocallyAvailable property has been removed (bug 1066826).
  • The preference network.websocket.enabled,true by default, has been removed; Websocket API cannot be deactivated anymore (bug 1091016).
  • The non-standard methods and properties of Window.crypto have been removed (bug 1030963). Only methods and properties defined in the standard WebCrypto API are left.
  • Our experimental implementation of WebGL 2.0 is going forward!
    • The WebGL2RenderingContext.copyBufferSubData() method has been implemented (bug 1048668).
Firefox 35

MathML

  • The dtls OpenType feature (via the CSS font-feature-settings on the default stylesheet) is now applied automatically to MathML elements when positioning scripts over it (e.g. dotless i with mathematical hat).

SVG

Audio/Video

No change.

Network & Security

  • HTTP/2 has been implemented and activated, with AEAD ciphers only (bug 1027720) and (bug 1047594).
  • The HTTP/2 alt-svc header is now supported (bug 1003448).
  • The Public Key Pinning Extension for HTTP (HPKP) has been implemented (bug 787133).
  • The CSP 1.1 base-uridirective is now supported (bug 1045897).
  • Path of the source is now considered too when host-source matching happens in CSP (bug 808292).

Changes for add-on and Mozilla developers

XUL & Add-ons

  • The private _getTabForBrowser() method on the <xul:tabbrowser> element has been deprecated. In its place, we've added a new, public, method called getTabForBrowser. This returns, predictably, the <xul:tab> element that contains the specified <xul:browser>.
  • Components.utils.now(), matching Performance.now() has been implemented for non-window chrome code (bug 969490).

Add-on SDK

Highlights

Firefox
  • Added access keys for context menu.
  • Removed isPrivateBrowsing from BrowserWindow.
  • added toJSON method to URL instances from sdk/url

Details

GitHub commits made between Firefox 34 and Firefox 35. This will not include any uplifts made after this release entered Aurora.

Bugs fixed between Firefox 34 and Firefox 35. Download kies 2.6 for mac. This will not include any uplifts made after this release entered Aurora.

See also

Older versions

Hi Andreas,

Mozilla Firefox 35.0.1 Download

I have a couple of question and would be glad if you can find some time to help me on. I have actually a customer EP 7.31, which was updated to SP14 recently. Accroding to the new stand, they would like to test also on last FF 35 and Chrome 40 versions, which are supported and tested due your statements and the PAM.

After first quite shallow tests EP looks good on both browsers. I have noticed some small problems apparently, before I open an OSS may I ask you 2 things please:

Mozilla Firefox 35

1.)Can we assume minor changes within the browser releases are also supported? Since FF and Chrome are updating themself automatically, my FF is e.g. 35.0.1. Or to be more generally: how can I found out if my current NW resp Portal version is matching a browser? In my case: EP 7.31 SP14 + latest patches is working well with FF 35.0.1 and Chrome 40.

2.)I remember we talk about this in short years ago, but to be sure: custom frameworks and custom application are not guaranteed to run well, right? My customer is using custom parts of AJAX framework (masthead) and mainly FPM applications. Im noticing some errors in rendering resp divergences comparing to IE, I guess we will not get any OSS support on this, right?

Firefox 35 Offline Installer

Thank you very much,

Mozilla Firefox 35.0 Windows 7

regards