--- title: 为开发者的 Firefox 68 文档 slug: Mozilla/Firefox/Releases/68 translation_of: Mozilla/Firefox/Releases/68 ---
{{FirefoxSidebar}}
本篇文章将提供关于在Firefox 68版本中,会影响到开发人员的更新的信息。Firefox 68版本发布于2019年7月9日。
字母间距
的滑条 ({{bug(1536237)}}).devtools.aboutdebugging.showSystemAddons
变为 devtools.aboutdebugging.showHiddenAddons
({{bug(1544372)}}).disabled
属性。 当 disabled
被设定在一个连同rel="stylesheet"
的 <link>
元素 , 引用的样式表不会在页面加载时被加载, 当 disabled
属性被改变为 false
或移除时,该样表会被加载 ({{bug(1281135)}})。<meta http-equiv="set-cookie">
({{bug(1457503)}})。scroll-padding
properties ({{bug(1373832)}})scroll-margin
properties ({{bug(1373833)}})::marker
pseudos ({{bug(1538618)}})ch
length unit so it now matches the spec (fallback for no '0' glyph, vertical metrics) ({{bug(282126)}})::part()
({{bug(1545430)}}) and ({{bug(1545425)}}).While we're keeping the prefixed versions of the various gradient properties ({{cssxref("linear-gradient")}}, {{cssxref("radial-gradient")}}, and {{cssxref("repeating-radial-gradient")}} available for compatibility reasons, we have revised how they're parsed so that they're handled much more like the non-prefixed versions. This means that certain existing styles won't work correctly.
In particular, the complicated syntax taking both an angle and a position will no longer work, and the to
keyword in the <side-or-corner>
parameter is not required for the prefixed gradient properties. You are encouraged to use the standard, non-prefixed gradient properties instead, as they're now widely supported ({{bug(1547939)}}).
scroll-snap-type:mandatory
will stop working. See the Firefox Site Compatability note.No changes.
noreferrer
is now supported; if specified, the new window's content is loaded without sharing the hostname, IP address, URL, or other identifying information about the host device ({{bug(1527287)}}).HTMLImageElement
is now implemented. This can be used to trigger loading and decoding of an image prior to adding it to the DOM ({{bug(1501794)}}).moz-chunked-arraybuffer
value for {{domxref("XMLHttpRequest.responseType", "responseType")}}. Code still using it should be updated to use the Fetch API as a stream ({{bug(1120171)}}).XMLHttpRequest
now outputs a warning to console if you perform a synchronous request while handling an {{domxref("Window.unload_event", "unload")}}, {{domxref("Window.beforeunload_event", "beforeunload")}}, or {{domxref("Window.pagehide_event", "pagehide")}} event ({{bug(980902)}}).preventScroll
option specifying whether or not to block the browser from scrolling the newly-focused element into view ({{bug(1374045)}}).null
candidate passed into the {{domxref("RTCPeerConnection.icecandidate", "icecandidate")}} event handler, indicating the receipt of a candidate, instead indicates that there are no further candidates coming; when this happens the ICE gathering ({{domxref("RTCPeerConnection.iceGatheringState", "iceGatheringState")}}) state reaches complete
({{bug(1318167)}}).{{domxref("MediaDevices.getUserMedia", "getUserMedia()")}} may no longer be used from a non-secure context; attempting to do so now throws a NotAllowedError
exception. Secure contexts are those loaded using HTTPS, those located using the file:///
scheme, and those loaded from localhost
. For now, if you must, you can re-enable the ability to perform insecure calls to getUserMedia()
by setting the preference media.getusermedia.insecure.enabled
to true
({{bug(1335740)}}).
Note: In the future, Firefox will also remove the {{domxref("navigator.mediaDevices")}} property on insecure contexts, preventing all access to the {{domxref("MediaDevices")}} APIs. This is already the case in Nightly builds.
token
value has been removed ({{bug(1529595)}}).executionContexts
directive. This was removed due to problems with interactions between interconnections among different kinds of data at different points in the navigation process and the way the specification is designed. It has been proposed that this directive be removed from the specification for this reason, among others ({{bug(1548034)}}).require-sri-for
is no longer supported due to concerns about its standardization status. It was previously available only behind a preference, which was off by default ({{bug(1386214)}}).WebDriver:SwitchToWindow
changes the selection to a different window it now waits for its focus
and activate
events before returning ({{bug(1335085)}}).TypeError: this.tabModal is null
failure, which sometimes appeared when interacting with modal dialogs or user prompts ({{bug(1538782)}})No changes.
proxy.register()
and proxy.unregister()
functions have been deprecated and will be removed from Firefox 71 ({{bug(1545811)}}).boolean
flag, incognito
, has been added to the proxy.RequestDetails. object. When true
, it indicates that this was a private browsing request ({{bug(1545163)}}).true
or false
) will be filtered out ({{bug(1548177)}}).string
value, cookieStoreId
, representing the cookie store ID of the current context, has been added to the proxy.RequestDetails. object ({{bug(1545420)}}).browser.tabs.duplicate()
now resolves immediately, before the tabs are completely loaded ({{bug(1394376)}}).无变更。
{{Firefox_for_developers(67)}}