Firefox 70 for developers
This article provides information about the changes in Firefox 70 that will affect developers. Firefox 70 was released on October 22, 2019.
- In the Debugger you can now set breakpoints for DOM Mutation, so execution will pause when a node or its attributes are changed or when a node is removed from the DOM (bug 1576219).
- The Debugger now shows an overlay on the page when it is paused, with basic stepping buttons to let you step and continue (bug 1574646).
- The Debugger now shows sources that already got discarded by the engine (usually scripts that execute once during page load), so you can properly set breakpoints to debug when they execute next (bug 1572280).
- The Debugger's scopes panel grouping has been simplified, consolidating additional scopes previously shown above the top level function (e.g. blocks created by
else) (bug 1448166)
- The Debugger now retains the currently selected and expanded variables in the scopes panel while stepping (bug 1405402).
- The Debugger now handles stepping over async functions correctly, making asynchronous function debugging easier (bug 1570178).
- When debugging in Container sessions (useful for testing different logins), the sources in the debugger are now shown correctly (bug 1375036).
debuggerstatements can be now disabled in the Debugger by setting a breakpoint on them and switching the breakpoints to "Never pause here" (bug 925269).
- WebExtensions developers can inspect
browser.storage.localfrom the Extension Storage item under the Storage tab (bug 1585499).
- An icon will be displayed next to inactive CSS properties in the Rules view of the Page Inspector, which you can hover over to get information on why it is inactive (bug 1306054).
- In the CSS Rules view, the color picker on foreground colors now tells you whether its contrast with the background color meets accessibility conformance criteria (bug 1478156).
- The Accessibility inspector's Check for issues dropdown now includes keyboard accessibility checks (bug 1564968).
- Firefox can now suggest securely-generated passwords to the user in the following situations:
<input>element has the
- The user opens the context menu on any password input element, even if it is not intended for new passwords.
- Opacity values like for
stop-opacitycan now be percentages (bug 1562086).
grid-auto-rowsnow accept multiple track-size values (bug 1339672).
- A number of text-related CSS properties have been enabled by default (bug 1573631):
displayproperty now accepts two keyword values representing the inner and outer display type (bug 1038294, bug 1105868 and bug 1557825).
font-sizeproperty now accepts the new keyword value
xxx-large. (bug 1553545).
:visitedpseudo-class no longer matches
<link>elements, for logic and performance reasons (bug 1572246; see Intent to ship: Make <link> elements always unvisited and [selectors] :link and <link> for more reasoning as to why).
- We now support an
autovalue for the
quotesproperty (bug 1421938).
- Stylesheets contained in
<style>elements are now cached for reuse, to improve performance (bug 1480146). Note that this currently doesn't include stylesheets that contain
<ratio>type now accepts
<number>/<number>or a single
<number>as a value. (bug 1565562).
- Cut, copy, and paste events are now dispatched to SVG graphics elements (bug 1569474).
- Numeric separators are now supported (bug 1435818).
Intl.RelativeTimeFormat.formatToParts()method has been implemented (bug 1473229).
BigInt.prototype.toLocaleString()method has been updated to work with the
optionsparameters per the ECMAScript 402 Intl API. Also,
BigIntvalues (bug 1543677).
- Per the latest ECMAScript specification, a leading zero is now never allowed for BigInt literals, making
09ninvalid similar to the existing error when legacy octal numbers like
07nare used. Always use a leading zero with the letter "o" (lowercase or uppercase) for octal
0755n). See bug 1568619.
- The Unicode extension key "nu" is now supported for the
Intl.RelativeTimeFormatconstructor and the
Intl.RelativeTimeFormat.resolvedOptions()method now also returns
go()methods are now asynchronous. Add a listener to the
popstateevent to get notification that navigation has completed bug 1563587.
- We've added support
DOMPoint, etc. in web workers (bug 1420580).
- A few more members have been moved from
Document.clearEvents(bug 1558570, bug 1558571).
- Notification permission can no longer be requested from inside a cross-origin
Media, Web Audio, and WebRTC
RTCPeerConnection.restartIce()method has been added. This is one of the four changes needed to implement the new "perfect negotiation" mechanism; the rest will come in future Firefox updates (bug 1551316).
RTCPeerConnection.setRemoteDescription()method can now be called with no parameters. This is another "perfect negotiation" update (bug 1568292).
MediaTrackSupportedConstraints.groupIdis now supported, and returns
MediaTrackConstraints.groupIdproperty is now supported (bug 1561254).
- Several new Web Audio API features have been implemented/updated:
AudioContext.getOutputTimestamp()implemented (bug 1324545).
AudioContext.outputLatencyimplemented (bug 1324552).
MediaStreamAudioSourceNode.mediaStreamimplemented (bug 1350973).
ChannelMergerNode()constructor now throws errors if you try to set
channelCountModeto invalid values (bug 1456263).
Canvas and WebGL
- The default referrer policy for third-party tracking resources is now
strict-origin-when-cross-originwhen Enhanced Tracking Protection is turned on (bug 1569996).
- The size of the
Refererrequest header is now limited to 4 KB (4,096 bytes). If an overly long referer exceeds the defined limit, only the origin part will be sent (bug 1557346).
- The HTTP cache is now partitioned per the top-level document's origin (bug 1536058).
- Updated the
WebDriver:TakeScreenshotcommand to be Fission compatible. It means that content from cross-origin iframes is now included in a page's screenshot. Or when using it from chrome scope that the active tab's content is visible now inside the browser window. (bug 1559592).
WebDriver:TakeScreenshotno longer accepts a list of DOM elements as used for highlighting (bug 1575511).
WebDriver:ExecuteAsyncScriptno longer sets
window.onunloadin ways that are web-exposed (bug 1568991).
- Added a new parameter to the
topSites.get()method that causes the method to return the list of pages that appear when the user opens a new tab (bug 1568617).
WebRTCIPHandlingPolicysub-property's permitted values have been amended (in bug 1452713) to match the behavior seen in Chrome as follows:
disable_non_proxied_udppreviously prevented the use of WebRTC if no proxy was configured. Now a proxy is always used if one is configured, but otherwise a non-proxied connection is permitted.
proxy_onlycan be used to provide the old behavior; this has the effect of only allowing ICE negotiation over TURN on TCP using a proxy; no other connections are allowed.
The following theme key properties, which provided aliases for theme keys used in chromium-based browsers, were removed:
headerURL, themes should now use
accentcolor, themes should now use
textcolor, themes should now use
- Hacks release post: Firefox 70 — a bountiful release for all
- Firefox 69 for developers
- Firefox 68 for developers
- Firefox 67 for developers
- Firefox 66 for developers
- Firefox 65 for developers
- Firefox 64 for developers
- Firefox 63 for developers
- Firefox 62 for developers
- Firefox 61 for developers
- Firefox 60 for developers
- Firefox 59 for developers
- Firefox 58 for developers
- Firefox 57 for developers
- Firefox 56 for developers
- Firefox 55 for developers
- Firefox 54 for developers
- Firefox 53 for developers
- Firefox 52 for developers
- Firefox 51 for developers
- Firefox 50 for developers
- Firefox 49 for developers
- Firefox 48 for developers
- Firefox 47 for developers
- Firefox 46 for developers
- Firefox 45 for developers
- Firefox 44 for developers
- Firefox 43 for developers
- Firefox 42 for developers
- Firefox 41 for developers
- Firefox 40 for developers
- Firefox 39 for developers