--- title: Firefox 65 pour développeurs slug: Mozilla/Firefox/Versions/65 translation_of: Mozilla/Firefox/Releases/65 ---
Cet article fournit des informations au sujet de changements introduits dans Firefox 65 qui vont concerner les développeurs. Firefox 65 a été publié le 29 janvier 2019.
$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
.disabled
attributes set on them ({{bug(329509)}}).src
attribute of an {{htmlelement("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.crisp-edges
value has now been unprefixed ({{bug(1496617)}}).auto
now resolves to auto
, rather than two colors ({{bug(1501418)}}).break-*
properties have been implemented, and the legacy page-break-*
properties have been aliased to them ({{bug(775618)}}):
anywhere
value has been implemented ({{bug(1505786)}}).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.meter
, which is now used as the default value for {{htmlelement("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 {{htmlelement("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 {{htmlelement("textarea")}} elements in UA stylesheets. the existing value textfield-multiline
is now an alias for textarea
({{bug(1507905)}})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 overriden by the all
value set on the parent element.contenteditable
elements nested inside contenteditable
elements are now selectable.user-select
now behaves consistently inside and outside shadow DOM.-moz-text
value has been removed.layout.css.shape-outside.enabled
pref has been removed; {{cssxref("shape-outside")}}, {{cssxref("shape-margin")}}, and {{cssxref("shape-image-threshold")}} can no longer be disabled in about:config
({{bug(1504387)}}).-moz-all
, -moz-text
, tri-state
, element
, elements
, and toggle
. See {{bug(1492958)}} and {{bug(1506547)}}.frames()
timing function has been removed ({{bug(1496619)}}).No changes.
2**30 - 2
(~1GB) instead of 2**28 - 1
(~256MB) ({{bug(1509542)}}).NetworkError
if the requested content type is a Blob
, and the request method is not GET
({{bug(1502599)}}).-moz-
prefixed versions of many of the {{domxref("Fullscreen API", "", "", "1")}} features have been deprecated, and will now display deprecation warnings in the JavaScript console when encountered ({{bug(1504946)}}).keyup
and keydown
events are now fired during IME composition, to improve cross-browser compatibility for CJKT users ({{bug(354358)}}, also seedata
property is now an empty string value rather than null
({{bug(1508824)}}).TypeError
if a non-valid URL is specified as the first parameter ({{bug(1503276)}}).pause
and resume
events (and their corresponding event handler properties — {{domxref("MediaRecorder.onpause")}} and {{domxref("MediaRecorder.onresume")}}) were not previously implemented, even though compatibility tables claimed they had been. They have now been implemented ({{bug(1458538)}}, {{bug(1514016)}}).currentTime
has been removed ({{bug(1502927)}}).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)}}).text
event — fired to notify the browser editor UI of IME composition string data and selection range — has been removed ({{bug(1288640)}}).No changes.
No 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)}}).
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)}}).
For unexpected alert open
errors more informative messages are provided (Bug 1502268).
image/webp
) has been added to the standard HTTP Request {{httpheader("Accept")}} header for HTML files ({{bug(1507691)}}).successorId
property, which can be used to store/retrieve the ID of the tab's successor.previousTabId
, which contains the ID of the previous activated tab, if it is still open.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 {{WebExtAPIRef("tabs.get()")}} and {{WebExtAPIRef("tabs.query()")}}.tabs.moveInSuccession()
allows manipulation of tab successors in bulk.No changes.
headerURL
/theme_frame
properties for Webextension themes are now supported on Firefox for Android ({{bug(1429488)}}).{{Firefox_for_developers(65)}}