Firefox 66 for developers

본 문서는, 개발자를 대상으로 Firefox 66에서 변경된 내용을 알려드립니다.

웹 개발자를 위한 변경사항

개발자 도구


  • UTF-8-encoded HTML (and plain text) files loaded from file: URLs are now supported without <meta charset="utf-8"> or the UTF-8 BOM, making it easier to work on such files locally before uploading them to a server. You still need to make sure that the server sends charset=utf-8 in the Content-Type HTTP header for such files, otherwise the detection mechanism used for local files would break incremental loading in the network case (bug 1071816).




추가사항 없음.



변경사항 없음.


New APIs/changes

  • Autoplaying audio will be blocked by default soon after 66 becomes the release version of Firefox (bug 1487844, see bug 1535667 for rollout details). The feature will be rolled out gradually to users until everyone has it.


DOM events

  • The InputEvent.inputType (en-US) property has been implemented (bug 1447239).
  • The Window.event and Event.returnValue (en-US) properties — originally proprietary IE features, then also supported across other browsers for compatibility purposes — have been re-introduced in Firefox 66, after first being added in versions 63 and 64 respectively but then removed again due to compatibility issues. 
  • From 66 onwards, when the KeyboardEvent.keyCode (en-US) property of the keypress (en-US) event object is 0, the value will be the same as KeyboardEvent.charCode (en-US). Conversely, when charCode is 0, it will be the same as keyCode. This mirroring behavior matches other browsers and is expected to solve most associated compatibility issues, however user agent sniffing might cause further issues in some JavaScript libraries. Note that in spec terms, we've switched from the split model to the conflated model (see How to determine keyCode for keypress events in the UI Event spec).

Media, Web Audio, and WebRTC

  • The MediaDevices method getDisplayMedia() (en-US), available as navigator.mediaDevices.getDisplayMedia(), has been added and synchronized with the specification. This method lets you capture a screen or part of a screen as a MediaStream (en-US) for manipulation or sharing (bug 1321221).
  • As a step toward eventually deprecating the Firefox-specific getUserMedia()-based method for capturing screen and window contents, the non-standard mediaSource constraint now treats the values screen and window identically. Both now present a list of both screens and windows for the user to choose from (bug 1474376).
  • qpSum (en-US) has been added to local outbound RTCRTPStreamStats (en-US) objects. This measures the total of the Quantization Parameter values for every frame sent or received on the video track. The higher this number, the more compressed the stream probably is (bug 1347070).
  • In a step along the road toward implementing support for Feature Policy in a future Firefox update, getUserMedia() can no longer be used in situations in which there is no proper origin for the content, such as when called from a sandboxed <iframe> or from a data URL entered into the address bar by the user. For more specifics and details, see Security in MediaDevices.getUserMedia() (bug 1371741).




변경사항 없음.


변경사항 없음.

애드온 개발자를 위한 변경사항

API 변화

  • Extension menu items of the "bookmark" type will also appear in the Bookmarks sidebar (Ctrl + B) and Library window (Ctrl + Shift + B) (bug 1419195).

Manifest changes

No changes.