1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
---
title: Firefox 69 for developers
slug: Mozilla/Firefox/Releases/69
translation_of: Mozilla/Firefox/Releases/69
original_slug: Mozilla/Firefox/Versions/69
---
<p>{{FirefoxSidebar}}{{Draft}}</p>
<p class="summary">This article provides information about the changes in Firefox 69 that will affect developers. Firefox 69 is the current <a href="https://www.mozilla.org/en-US/firefox/channel/desktop/#beta">Beta version of Firefox</a>, and will ship on <a href="https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates" rel="noopener">September 3, 2019</a>.</p>
<h2 id="Changes_for_web_developers">Changes for web developers</h2>
<h3 id="Developer_tools">Developer tools</h3>
<ul>
<li>An icon will be displayed next to invalid or unsupported <a href="/en-US/docs/Tools/Page_Inspector/How_to/Examine_and_edit_CSS#Examine_CSS_rules">CSS rules</a> in the Rules pane of the Page Inspector ({{bug(1306054)}}).</li>
<li>The debugger now includes the ability to set a breakpoint on event handlers. For example, you can select keydown, and execution will pause when it enters any keydown event handler in your project ({{bug(1526079)}}).</li>
<li>When you hover over an element in the Page Inspector, the infobar that appears now includes the fact that an element is a flex container, or flex item ({{bug(1521188)}}).</li>
</ul>
<h4 id="Removals">Removals</h4>
<h3 id="HTML">HTML</h3>
<ul>
<li>In order to align more closely to the specification, the text track associated with a {{HTMLElement("track")}} element no longer loads the WebVTT file containing the text cues if the element is created in its default <code>disabled</code> {{domxref("TextTrack.mode", "mode")}}. To access or manipulate the cues when the <code>mode</code> is <code>disabled</code>, change the <code>mode</code> to either <code>started</code> or <code>hidden</code>; this will trigger loading of the WebVTT data ({{bug(1550633)}}).</li>
</ul>
<h4 id="Removals_2"> Removals</h4>
<ul>
<li>The HTML {{HTMLElement("keygen")}} element has been removed from Firefox. It was deprecated some time ago, and its purpose has generally been supplanted by other technologies ({{bug(1315460)}}).</li>
</ul>
<h3 id="CSS">CSS</h3>
<ul>
<li>Implement the break-spaces value of the white-space property ({{bug(1351432)}}).</li>
<li>Implement SVG geometry properties in CSS ({{bug(1383650)}}).</li>
<li>The {{cssxref("::cue")}} selector—used to style the captions ("cues") displayed by <a href="/en-US/docs/Web/API/WebVTT_API">WebVTT</a>—now enforces the limitations on which CSS properties may be used within cues, per the specification.</li>
<li>Properties which may apply to `::marker` restricted as per the specification ({{bug(1552578)}})</li>
<li>The {{cssxref("overflow-block")}} and {{cssxref("overflow-inline")}} properties have been implemented ({{bug(1470695)}}).</li>
<li>Adds the ability to test for support of a selector when using CSS Feature Queries (<a href="/en-US/docs/Web/CSS/@supports">@supports</a>), with the `selector()` method ({{bug(1513643)}}).</li>
<li>The {{cssxref("user-select")}} property—which specifies whether or not the user is able to select text in the affected element—has been unprefixed in Firefox 69 ({{bug(1492739)}}).</li>
</ul>
<h4 id="Removals_3">Removals</h4>
<h3 id="SVG">SVG</h3>
<ul>
<li>Support gzip-compressed SVG-in-OpenType ({{bug(1359240)}}).</li>
</ul>
<h4 id="Removals_4">Removals</h4>
<h3 id="JavaScript">JavaScript</h3>
<ul>
<li>The promise rejection events, <code><a href="/en-US/docs/Web/API/Window/unhandledrejection_event">unhandledrejection</a></code> and <code><a href="/en-US/docs/Web/API/Window/rejectionhandled_event">rejectionhandled</a></code>, are now enabled by default ({{bug(1362272)}}). To learn more about how these work, see {{SectionOnPage("/en-US/docs/Web/JavaScript/Guide/Using_promises", "Promise rejection events")}}.</li>
</ul>
<h4 id="Removals_5">Removals</h4>
<h3 id="HTTP">HTTP</h3>
<ul>
<li>The HTTP headers {{HTTPHeader("Access-Control-Expose-Headers")}}, {{HTTPHeader("Access-Control-Allow-Methods")}}, and {{HTTPHeader("Access-Control-Allow-Headers")}} now accept a wildcard value "<code>*</code>" for requests without credentials ({{bug(1309358)}}). This change has also been uplifted to Firefox 68 ESR.</li>
</ul>
<h3 id="APIs">APIs</h3>
<p><em>No changes.</em></p>
<h4 id="New_APIs">New APIs</h4>
<h4 id="DOM">DOM</h4>
<ul>
<li>The {{domxref("DOMMatrix")}}, {{domxref("DOMPoint")}}, and related objects are now supported in workers ({{bug(1420580)}}).</li>
</ul>
<h4 id="DOM_events">DOM events</h4>
<h4 id="Service_workers">Service workers</h4>
<h4 id="Media_Web_Audio_and_WebRTC">Media, Web Audio, and WebRTC</h4>
<ul>
<li>For improved user security, and in keeping with the latest versions of the <a href="/en-US/docs/Web/API/Media_Streams_API">Media Capture and Streams</a> specification, the {{domxref("navigator.mediaDevices")}} property is no longer present if the context is insecure. To use {{domxref("MediaDevices.getUserMedia", "getUserMedia()")}}, {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}}, {{domxref("MediaDevices.enumerateDevices", "enumerateDevices()")}}, and so forth, be sure your content is loaded using {{Glossary("HTTPS")}} ({{bug(1528031)}}).</li>
<li>The Web Audio API's {{domxref("AudioParam.value")}} property now returns the actual value of the property at the current time, taking into account all scheduled or gradiated changes taking places to the value. Previously, Firefox only returned the most recent explicitly-set value (as through using the <code>value</code> setter) ({{bug(893020)}}).</li>
<li>Updated {{domxref("MediaStreamAudioSourceNode")}} to use the new, lexicographical, ordering for tracks. Previously, track ordering was up to the individual browser, and could even change arbitrarily. In addition, attempting to create a <code>MediaStreamAudioSourceNode</code> using a stream that has no audio tracks now throws an <code>InvalidStateError</code> exception ({{bug(1553215)}}).</li>
<li>The {{domxref("MediaTrackSettings.facingMode", "facingMode")}}, {{domxref("MediaTrackSettings.deviceId", "deviceId")}}, and {{domxref("MediaTrackSettings.groupId", "groupId")}} settings are now included as members of the {{domxref("MediaTrackSettings")}} object returned by calls to {{domxref("MediaStreamTrack.getSettings()")}} ({{bug(1537986)}}).</li>
</ul>
<h4 id="Canvas_and_WebGL">Canvas and WebGL</h4>
<h4 id="Removals_6">Removals</h4>
<h3 id="Security">Security</h3>
<p><em>No changes.</em></p>
<h4 id="Removals_7">Removals</h4>
<h3 id="Plugins">Plugins</h3>
<p><em>No changes.</em></p>
<h4 id="Removals_8">Removals</h4>
<h3 id="Other">Other</h3>
<p><em>No changes.</em></p>
<h4 id="Removals_9">Removals</h4>
<h2 id="Changes_for_add-on_developers">Changes for add-on developers</h2>
<h3 id="API_changes">API changes</h3>
<p><em>No changes.</em></p>
<h4 id="Removals_10">Removals</h4>
<h3 id="Manifest_changes">Manifest changes</h3>
<p><em>No changes.</em></p>
<h4 id="Removals_11">Removals</h4>
<h2 id="See_also">See also</h2>
<ul>
<li><a href="https://www.fxsitecompat.com/en-CA/versions/69/">Site compatibility for Firefox 69</a></li>
</ul>
<h2 id="Older_versions">Older versions</h2>
<p>{{Firefox_for_developers(68)}}</p>
|
