当前位置：文江博客知识库 en-US 文档 Mozilla Firefox Releases 65

Firefox 65 for developers 编辑

This article provides information about the changes in Firefox 65 that will affect developers. Firefox 65 was released on January 29, 2019.

Changes for web developers

Developer tools

The Flexbox inspector is now enabled by default.
Support has been added to the JavaScript Debugger for XHR Breakpoints (bug 821610).
Right-click on an item in the accessibility tree from the Accessibility viewer to print it as json to the JSON viewer.
The color contrast display of the Accessibility Picker has been updated so that if a text's background is complex (e.g. a gradient or complex image), it shows a range of color contrast values.
The Headers tab of the Network Monitor now displays the Referrer Policy for the selected request (bug 1496742).
When displaying stack traces (e.g. in console logs or the JavaScript debugger), calls to framework methods are identified and collapsed by default, making it easier to home in on your code.
In the same fashion as native terminals, you can now use reverse search to find entries in your JavaScript console history (F9 on Windows/Linux or Ctrl + R on macOS, then type a search term, followed by Ctrl + R/Ctrl + S to toggle through results).
The JavaScript console's $0 shortcut (references the currently inspected element on the page) now has autocomplete available, so for example you could type $0.te to get autocomplete suggestions for properties like $0.textContent.
The edits you make in the Rules view of the Inspector are now listed in the Changes panel (bug 1503920).

HTML

Events are now dispatched on disabled HTML elements, i.e. <button>, <fieldset>, <input>, <select>, and <textarea> elements with disabled attributes set on them (bug 329509).
Removing the src attribute of an <iframe> element now causes about:blank to be loaded into it, giving it parity with Chrome and Safari (bug 1507842). Previously removing src had no effect on the iframe content.
We have added support for the referrerpolicy attribute on <script> elements (bug 1460920).

CSS

The image-rendering property's crisp-edges value has now been unprefixed (bug 1496617).
A scrollbar-color value of auto now resolves to auto, rather than two colors (bug 1501418).
The break-* properties have been implemented, and the legacy page-break-* properties have been aliased to them (bug 775618):
- break-before is now an alias for page-break-before.
- break-after is now an alias for page-break-after.
- break-inside is now an alias for page-break-inside.
The overflow-wrap property's anywhere value has been implemented (bug 1505786).
The new step position keywords jump-start, jump-end, jump-none, and jump-both — usable inside the steps() timing function — have been implemented (bug 1496619). This also coincides with the removal of the frames() timing function, which was the previous way of implementing such functionality, now deprecated.
Some new -webkit-appearance values have been added, for compatibility with other browsers. In particular:
- meter, which is now used as the default value for <meter> elements in UA stylesheets. the existing value meterbar is now an alias for meter (bug 1501483).
- progress-bar, which is now used as the default value for <progress> elements in UA stylesheets. the existing value progressbar is now an alias for progress-bar (bug 1501506).
- textarea, which is now used as the default value for <textarea> elements in UA stylesheets. the existing value textfield-multiline is now an alias for textarea (bug 1507905)
The behavior of user-select has been changed to make it align more with other browsers (bug 1506547). Specifically:
- user-select: all set on an element no longer overrides other values of user-select set on children of that element. So for example in the following snippet:
```
<div style="-webkit-user-select: all">All
  <div style="-webkit-user-select: none">None</div>
</div>
```
  The <div> with none set on it is now non-selectable. Previously this value would have been overridden by the all value set on the parent element.
- non-contenteditable elements nested inside contenteditable elements are now selectable.
- user-select now behaves consistently inside and outside shadow DOM.
- The proprietary -moz-text value has been removed.
CSS environment variables (the env() function) have been implemented (bug 1462233).

Removals

The layout.css.shape-outside.enabled pref has been removed; shape-outside, shape-margin, and shape-image-threshold can no longer be disabled in about:config (bug 1504387).
Several Firefox-only values of the user-select property have been removed — -moz-all, -moz-text, tri-state, element, elements, and toggle. See bug 1492958 and bug 1506547.
As mentioned above, the frames() timing function has been removed (bug 1496619).

SVG

No changes.

JavaScript

Intl.RelativeTimeFormat is now supported (bug 1504334).
Strings now have a maximum length of 2**30 - 2 (~1GB) instead of 2**28 - 1 (~256MB) (bug 1509542).
The globalThis property, which always refers to the top-level global object, has been implemented (bug 1317422).

APIs

New APIs

Readable Streams have been enabled by default (bug 1505122).
The Storage Access API has been enabled by default (bug 1513021).

DOM

Performance.toJSON() has been exposed to Web Workers (bug 1504958).
XMLHttpRequest requests will now throw a NetworkError if the requested content type is a Blob, and the request method is not GET (bug 1502599).
The -moz- prefixed versions of many of the Fullscreen API features have been deprecated, and will now display deprecation warnings in the JavaScript console when encountered (bug 1504946).
createImageBitmap() now supports SVG images (SVGImageElement) as an image source (bug 1500768).

DOM events

Going forward, only one Window.open() call is allowed per event (bug 675574).
The keyup and keydown events are now fired during IME composition, to improve cross-browser compatibility for CJKT users (bug 354358, also see
keydown and keyup events are now fired during IME composition for more useful details).

Web workers

SharedWorkerGlobalScope.onconnect's event object is a MessageEvent instance — its data property is now an empty string value rather than null (bug 1508824).

Fetch and Service workers

The Response.redirect() method now correctly throws a TypeError if a non-valid URL is specified as the first parameter (bug 1503276).
The ServiceWorkerContainer.register() and WorkerGlobalScope.importScripts() (when used by a service worker) methods will now accept any files with a valid JavaScript MIME type (bug 1354577).
The FetchEvent.replacesClientId and FetchEvent.resultingClientId properties are now supported (bug 1264177).
The ServiceWorkerGlobalScope.onmessageerror and ServiceWorkerContainer.onmessageerror handler properties have been implemented (bug 1399446).
The Origin header is no longer set on Fetch requests with a method of HEAD or GET (bug 1508661).

Media, Web Audio, and WebRTC

The WebRTC RTCIceCandidateStats dictionary has been updated according to the latest spec changes (bug 1324788, bug 1489040; see also
RTCIceCandidateStats has been updated to the latest spec for more details on exactly what has changed).
The MediaRecorder pause and resume events (and their corresponding event handler properties — MediaRecorder.onpause and MediaRecorder.onresume) were not previously implemented, even though compatibility tables claimed they had been. They have now been implemented (bug 1458538, bug 1514016).

Canvas and WebGL

The WebGL EXT_texture_compression_bptc and EXT_texture_compression_rgtc texture compression extensions have been exposed to WebGL1 and WebGL2 contexts (bug 1507263).

Removals

Mutation events have been disabled in shadow trees (bug 1489858).
The non-standard MediaStream property currentTime has been removed (bug 1502927).
The dom.webcomponents.shadowdom.enabled and dom.webcomponents.customelements.enabled prefs have been removed — Shadow DOM and Custom Elements can no longer be disabled in about:config (bug 1503019).
The non-standard DOM text event — fired to notify the browser editor UI of IME composition string data and selection range — has been removed (bug 1288640).
The keypress event is no longer fired for non-printable keys (bug 968056), except for the Enter key, and the Shift + Enter and Ctrl + Enter key combinations (these were kept for cross-browser compatibility purposes).

Security

Additional CORS restrictions are now being enforced on allowable request headers (bug 1483815, see also whatwg fetch issue 382: CORS-safelisted request headers should be restricted according to RFC 7231 for more details).

Networking

No changes.

Plugins

No changes.

WebDriver conformance (Marionette)

API changes

WebDriver:ElementSendKeys now handles <input type=file> more relaxed for interactability checks, and allows those elements to be hidden without raising a not interactable error anymore. If a strict interactability check is wanted the capability strictFileInteractability can be used (bug 1502864).

Bug fixes

The window manipulation commands WebDriver:FullscreenWindow, WebDriver:MinimizeWindow, WebDriver:MaximizeWindow, and WebDriver:SetWindowRect have been made more stable (bug 1492499). It means that under special conditions they don't cause an infinite hang anymore, but instead timeout after 5s if the requested window state cannot be reached (bug 1521527).
WebDriver:ElementClick now correctly calculates the center point of the element to click, which allows interactions with dimensions of 1x1 pixels (bug 1499360).

Others

For unexpected alert open errors more informative messages are provided (bug 1502268).

Other

Support for WebP images has been added (bug 1294490).
- In addition, to facilitate cross-browser compatibility in certain situations the WebP MIMEType (image/webp) has been added to the standard HTTP Request Accept header for HTML files (bug 1507691).
The AV1 codec is now supported by default on Windows (bug 1452146).

Changes for add-on developers

API changes

Tabs

The tabs API has been enhanced to support tab successors — a tab can have a successor assigned to it, which is the ID of the tab that will be active once it is closed (bug 1500479, also see this blog post for more information). In particular:
- The tabs.Tab type now has a successorId property, which can be used to store/retrieve the ID of the tab's successor.
- The tabs.onActivated event listener's callback has a new parameter available, previousTabId, which contains the ID of the previous activated tab, if it is still open.
- The tabs.update() function's updateProperties object has a new optional property available on it, successorTabId, so can be used to update it.
- successorTabId is also returned by functions like tabs.get() and tabs.query().
- The new function tabs.moveInSuccession() allows manipulation of tab successors in bulk.