Firefox 43 for developers

Highlights:

• Server logging in the Web Console
• Quickly find the rule that overrode a CSS declaration
• "Use in Console" context menu item in Inspector
• "Strict" option for filtering in the Rules view
• Network entries in the Console now link to the Network Monitor
• Markup view shows indicators for pseudo-classes locked for elements
• New sidebar UI for WebIDE

All devtools bugs fixed between Firefox 42 and Firefox 43.

• Support for the standard, unprefixed version of hyphens has been landed (Firefox bug 953408).
• The shorthand property font has been updated to accept font-stretch values (Firefox bug 1057680).
• To match a latest evolution of the specification, the :fullscreen pseudo-class now selects the whole stack of elements in full screen, and not only the top-level one (Firefox bug 1199522).
• The deprecated SVG values for the writing-mode, lr, lr-tb, rl, tb, and tb-rl, have been added in CSS as aliases to standard properties (Firefox bug 1205787).

• For <img> with ICO image containing multiple frames, the intrinsic dimension of the image is set to the one of the largest frame, and no more of the smallest frame Firefox bug 1201796.
• The value of the document's viewport (defined with <meta name="viewport>)can now dynamically be changed via JavaScript (Firefox bug 976616).

New APIs

• The new ES2016 methods Array.prototype.includes() and TypedArray.prototype.includes() are now enabled by default (Firefox bug 1070767).

Changes regarding the arguments object

• To match the ES2015 specification, arrow functions no longer have their own arguments object. The arguments object is now lexically bound (inherited from the outer function). In most cases, rest parameters are a good alternative (...args) => args[i], see Firefox bug 889158.
• The arguments object is now allowed in conjunction with rest parameters (Firefox bug 1133298).
• From now on, a mapped arguments object in non-strict functions is only provided if the function does not contain any rest parameters, any default parameters or any destructured parameters (Firefox bug 1175394).

Other changes

• Generators and generator methods are no longer constructable as per ES2016 (Firefox bug 1191486).

DOM & HTML DOM

No change.

IndexedDB

• A new feature called locale-aware sorting has been added allowing for the creation of indexes with a locale specified, which can then be used to sort data according to the rules of that locale (Firefox bug 871846). This is a non-standard Firefox-specific feature.

Service Workers

• As per the specification, if ExtendableEvent.waitUntil() is called outside of the ExtendableEvent handler, Firefox will now throw an InvalidStateError; in addition, multiple calls to waitUntil() will now stack up, and the resulting promises will be added to the list of extend lifetime promises (Firefox bug 1180274).
• PushMessageData methods have been implemented (Firefox bug 1149195).

WebRTC

• The HTMLCanvasElement.captureStream() method has been activated by default (Firefox bug 1177276).
• The non-standard constraint style option list for RTCOfferOptions has been deprecated and will be removed entirely in Firefox 44.

Miscellaneous

• The Battery Status API now uses the new promise syntax for Navigator.getBattery(), as specified in the recent evolution of the specification (Firefox bug 1050749).
• The User-Agent header is no longer in the list of forbidden header names so it can now be set in a Fetch Headers object, via XHR XMLHttpRequest.setRequestHeader(),… (Firefox bug 1188932).
• The MediaRecorder() constructor can now accept an options dictionary as a parameter, which allows you to set custom bitrates for the audio/video to be recorded (Firefox bug 1161276).
• The PerformanceObserver interface, belonging to the Performance Timeline API has been implemented (Firefox bug 1165796).
• The Frame Timing API has been added: the PerformanceRenderTiming and PerformanceCompositeTiming interfaces are now available (Firefox bug 1191178).
• The modern Screen Orientation API has been implemented: unprefixed Screen.orientation and the ScreenOrientation interface are now available (Firefox bug 1131470). The non-standard Screen.mozOrientation, Screen.onmozorientationchange, Screen.mozLockOrientation(), and Screen.mozUnlockOrientation() will be removed in the future.
• Under Linux, like under Windows, Event.timeStamp now returns a DOMHighResTimeStamp (Firefox bug 1026803).
• Experimental support for Selection events selectionchange and selectstart, as well as the Document.onselectionchange and HTMLInputElement.onselectstart event handlers property has been added (Firefox bug 571294). The selectionchange event is fired on the Document if the associated Selection object is concerned, or on the specific HTMLInputElement or HTMLTextAreaElement (Firefox bug 1196479). This feature is controlled by the dom.select_events.enabled preference, that defaults to false, except on Nightly.
• Support for MouseEvent.offsetX and MouseEvent.offsetY have been activated on Firefox for Android and Firefox OS (Firefox bug 1204841).
• The HTMLCanvasElement.mozFetchAsStream() method has been removed (Firefox bug 1206030).
• The constructor Request() as well as fetch() will now raise a TypeError exception when used with a URL containing a username and password (Firefox bug 1195820).

No change.

No change.

No change.

No change.

No change.

• Access to Web Storage (i.e. localStorage and sessionStorage) from third-party IFrames is now denied if the user has disabled third-party cookies (Firefox bug 536509).
• This whitelist has even been removed in Nightly and Aurora/Dev Edition of the browser (Firefox bug 1201023). It is currently scheduled that this removal will also happen for Beta and Release versions for the next version (Firefox 44).
• Subresource integrity has been implemented for <script> and <link> that links to stylesheets (Firefox bug 992096).

No change.

No change.

No change.

No change.

• In preparation for future releases to switch over to multi-process content, NPAPI plugins can no longer be run in the same process as the page content. The preferences starting with dom.ipc.plugins are no longer used.

No change.