You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-edge/web-platform/release-notes/134.md
+18-21Lines changed: 18 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ For WebView2, see [Release Notes for the WebView2 SDK](../../webview2/release-no
65
65
<!-- ---------- -->
66
66
###### `:has-slotted` pseudo selector
67
67
68
-
The `:has-slotted` pseudo class represents a slot element with slotted content, such as a text node or element. This can be used to style elements based on whether or not they are using slot fallback content.
68
+
The `:has-slotted` pseudo class represents a slot element with slotted content, such as a text node or element. This can be used to style elements based on whether or not they are using slot fallback content.
69
69
70
70
See [:has-slotted](https://developer.mozilla.org/docs/Web/CSS/:has-slotted) at MDN.
71
71
@@ -81,7 +81,7 @@ See [Attribution Reporting API](https://developer.mozilla.org/docs/Web/API/Attri
81
81
<!-- ---------- -->
82
82
###### CSS highlight inheritance
83
83
84
-
With CSS highlight inheritance, the pseudo-classes such as `::selection` and `::highlight` now inherit their properties through the pseudo highlight chain, rather than the element chain. The result is a more intuitive model for inheritance of properties in highlights.
84
+
With CSS highlight inheritance, the pseudo-classes such as `::selection` and `::highlight` now inherit their properties through the pseudo highlight chain, rather than the element chain. The result is a more intuitive model for inheritance of properties in highlights.
85
85
86
86
When any supported property is not given a value by the cascade, its specified value is determined by inheritance from the corresponding highlight pseudo-element of its originating element's parent.
87
87
@@ -101,27 +101,27 @@ Using this property, webpages that display HDR images can limit their brightness
101
101
102
102
The customizable `<select>` element allows developers to take complete control of the rendering of the element, by adding the `appearance: base-select` CSS declaration.
103
103
104
-
This feature currently relies on the `SelectParserRelaxation` flag, which changes the HTML parser to allow more tags within the `<select>` tag. Sites which include additional tags inside `<select>` which were getting removed before, such as `<span>`s, or are including an extremely large number of `<option>`s may be affected by `SelectParserRelaxation`.
104
+
This feature currently relies on the `SelectParserRelaxation` flag, which changes the HTML parser to allow more tags within the `<select>` tag. Sites which include additional tags inside `<select>` which were getting removed before, such as `<span>`s, or are including an extremely large number of `<option>`s may be affected by `SelectParserRelaxation`.
105
105
106
106
See [Customizable Select Element (Explainer)](https://open-ui.org/components/customizableselect/).
107
107
108
108
109
109
<!-- ---------- -->
110
110
###### `<dialog>` light dismiss
111
111
112
-
This feature adds the _light dismiss_ behavior of the Popover API to `<dialog>` elements. Light dismissing is the act of closing the `<dialog>` element by clicking or tapping outside of the element.
112
+
This feature adds the _light dismiss_ behavior of the Popover API to `<dialog>` elements. _Light dismissing_ means closing the `<dialog>` element by clicking or tapping outside of the element.
113
113
114
114
A new `closedby` attribute controls the behavior:
115
115
116
116
*`<dialog closedby="none">`: no user-triggered closing of dialogs at all.
117
117
*`<dialog closedby="closerequest">`: user pressing ESC (or another close trigger) closes the dialog.
118
-
*`<dialog closedby="any">`: user clicking outside the dialog, or pressing ESC, closes the dialog. Akin to `popover=auto` behavior.
118
+
*`<dialog closedby="any">`: user clicking outside the dialog, or pressing ESC, closes the dialog. Similar to `popover=auto` behavior.
119
119
120
120
121
121
<!-- ---------- -->
122
122
###### `application-title` meta tag for installed web apps
123
123
124
-
The `<meta name="application-title">` element allows developers of installed web applications to set the text that appears in the title bar of the installed application window. By default, if the `application-title` meta name is missing, the text contained in the HTML `<title>` element is used instead.
124
+
The `<meta name="application-title">` element allows developers of installed web applications to set the text that appears in the title bar of the installed application window. By default, if the `application-title` meta name is missing, the text that's contained in the HTML `<title>` element is used instead.
125
125
126
126
See [Other names](https://developer.mozilla.org/docs/Web/HTML/Element/meta/name#other_names), in _Standard metadata names_, at MDN.
127
127
@@ -131,28 +131,28 @@ See [Other names](https://developer.mozilla.org/docs/Web/HTML/Element/meta/name#
131
131
132
132
In Document-Policy, the `expect-no-linked-resources` configuration point allows a document to hint the browser to better optimize its loading sequence, such as by not using the default speculative parsing behavior.
133
133
134
-
Browsers have implemented speculative parsing of HTML to speculatively fetch resources that are present in the HTML markup, to speed up page loading. For the vast majority of web pages that have resources declared in the HTML markup, the optimization is beneficial and the cost paid in determining such resources is a sound tradeoff. However, the following scenarios might result in a sub-optimal performance tradeoff vs. the explicit time spent parsing HTML for determining subresources to fetch:
134
+
Browsers have implemented speculative parsing of HTML to speculatively fetch resources that are present in the HTML markup, to speed up page loading. For the vast majority of web pages that have resources declared in the HTML markup, the optimization is beneficial and the cost paid in determining such resources is a sound tradeoff. However, the following scenarios might result in a sub-optimal performance tradeoff vs. the explicit time spent parsing HTML for determining sub-resources to fetch:
135
135
136
136
* Pages that do not have any resources declared in the HTML.
137
137
* Large HTML pages with minimal or no resource loads that could explicitly control preloading resources via other preload mechanisms available.
138
138
139
-
The `expect-no-linked-resources` Document-Policy hints the browser that it may choose to optimizeout the time spent in such subresource determination.
139
+
The `expect-no-linked-resources` Document-Policy hints to the browser that the browser is allowed to optimize-out the time that's spent in such sub-resource determination.
140
140
141
141
142
142
<!-- ---------- -->
143
143
###### Explicit resource management
144
144
145
-
This feature introduces the `using` keyword to JavaScript, which allows developers to explicitly manage resources. The `using` keyword is used to define a block of code that uses a resource, and ensures that the resource is disposed of when the block is exited. This feature addresses a common pattern in software development regarding the lifetime and management of various resources (memory, I/O, etc.). This pattern generally includes the allocation of a resource and the ability to explicitly release critical resources.
145
+
This feature introduces the `using` keyword to JavaScript, which allows developers to explicitly manage resources. The `using` keyword is used to define a block of code that uses a resource, and ensures that the resource is disposed of when the block is exited. This feature addresses a common pattern in software development regarding the lifetime and management of various resources (such as memory or I/O). This pattern supports resource allocation and explicitly releasing critical resources.
146
146
147
147
See [ECMAScript Explicit Resource Management](https://github.com/tc39/proposal-explicit-resource-management).
148
148
149
149
150
150
<!-- ---------- -->
151
151
###### Extend the `console.timeStamp` API to support measurements and presentation options
152
152
153
-
This feature extends the `console.timeStamp()` API, in a backwards-compatible manner, to provide a high-performance method for instrumenting applications and surfacing timing data to the **Performance** tool in DevTools.
153
+
This feature extends the `console.timeStamp()` API, in a backwards-compatible manner, to provide a high-performance method for instrumenting applications and surfacing timing data to the **Performance** tool in DevTools.
154
154
155
-
Timing entries added with the API can have a custom timestamp, duration, and presentation options such as the color to be used in the **Performance** tool for the entry.
155
+
Timing entries that are added by using this API can have a custom timestamp, duration, and presentation options, such as which color to use for the entry in the **Performance** tool.
156
156
157
157
See also:
158
158
@@ -174,49 +174,46 @@ See [CanvasRenderingContext2D: getContextAttributes() method](https://developer.
174
174
175
175
Enables Shared Storage callers to customize the number of contributions per Private Aggregation report.
176
176
177
-
This feature enables Shared Storage callers to configure per-context contribution limits via a new field: `maxContributions`. Callers set this field to override the default number of contributions per report — larger and smaller numbers will both be permitted. Due to padding, the size of each report's payload will be roughly proportional to the chosen number of contributions per report.
177
+
This feature enables Shared Storage callers to configure per-context contribution limits via a new field: `maxContributions`. Callers set this field to override the default number of contributions per report — larger and smaller numbers will both be permitted. Due to padding, the size of each report's payload will be roughly proportional to the chosen number of contributions per report.
178
178
179
179
See also:
180
-
181
180
*[Sign up for the Ad Selection API](../ad-selection-api.md)
182
181
183
182
184
183
<!-- ---------- -->
185
184
###### Support `imageSmoothingQuality` in CSS Painting API
186
185
187
-
This feature adds support for the `imageSmoothingQuality` attribute on the `PaintRenderingContext2D` interface. This allows web developers to make quality and performance tradeoffs when scaling images created from the CSS Painting API. The `imageSmoothingQuality` attribute supports three options: low, medium, and high.
186
+
This feature adds support for the `imageSmoothingQuality` attribute on the `PaintRenderingContext2D` interface. This allows you to make quality and performance tradeoffs when scaling images that were created by using the CSS Painting API. The `imageSmoothingQuality` attribute supports three options: low, medium, and high.
188
187
189
188
See also:
190
-
191
189
*[CSS Painting API](https://developer.mozilla.org/docs/Web/API/CSS_Painting_API) at MDN.
192
190
*[CanvasRenderingContext2D: imageSmoothingQuality property](https://developer.mozilla.org/docs/Web/API/CanvasRenderingContext2D/imageSmoothingQuality) at MDN.
193
191
194
192
195
193
<!-- ---------- -->
196
194
###### WebGPU Subgroups
197
195
198
-
The subgroups WbGPU feature allows SIMD parallelism. With subgroups, threads within a group can perform collective operations. This provides efficient communication and data sharing among groups of invocations. These operations can be used to accelerate applications by reducing memory overheads incurred by inter-invocation communication.
196
+
The subgroups WbGPU feature allows SIMD parallelism. By using subgroups, threads within a group can perform collective operations. This provides efficient communication and data sharing among groups of invocations. These operations can be used to accelerate applications, by reducing memory overhead that's incurred by inter-invocation communication.
199
197
200
198
See [WebGPU API](https://developer.mozilla.org/docs/Web/API/WebGPU_API) at MDN.
201
199
202
200
203
201
<!-- ---------- -->
204
202
###### `fetchLater()`
205
203
206
-
The `fetchLater()` JavaScript method requests a deferred fetch. Once called, the network request is queued by the browser and will be invoked in one of the following scenarios:
207
-
204
+
The `fetchLater()` JavaScript method requests a deferred fetch. After this method is called, the network request is queued by the browser, and is then invoked either:
208
205
* When the document is destroyed.
209
-
* After a certain time.
206
+
* After a certain time.<!-- todo: after a specified duration? -->
210
207
211
-
The method returns a `FetchLaterResult` that contains a boolean field which value is updated when the deferred request has been sent. When the request is successfully sent, the response is ignored by browser, including its body and headers.
208
+
The method returns a `FetchLaterResult` that contains a boolean field. The value of the boolean field is updated when the deferred request has been sent. When the request is successfully sent, the response is ignored by browser, including its body and headers.
212
209
213
210
See [Window: fetch() method](https://developer.mozilla.org/docs/Web/API/Window/fetch) at MDN.
The following are new experimental APIs which you can try on your own live website for a limited time. To learn more about origin trials, see [Use origin trials in Microsoft Edge](../../origin-trials/index.md). To see the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
216
+
The following are new experimental APIs which you can try on your own live website for a limited time. To learn more about origin trials, see [Use origin trials in Microsoft Edge](../../origin-trials/index.md). To see the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
0 commit comments