Skip to content

Commit d7310f7

Browse files
committed
del leading space
1 parent 97c0563 commit d7310f7

2 files changed

Lines changed: 5 additions & 5 deletions

File tree

microsoft-edge/web-platform/release-notes/134.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -207,9 +207,9 @@ See [Window: fetch() method](https://developer.mozilla.org/docs/Web/API/Window/f
207207

208208
This feature makes concurrent execution of shared storage worklets more reliable by integrating the Web Locks API into Shared Storage.
209209

210-
* `navigator.locks.request()` is available to worklet environments.
211-
* All modifier methods support the option `{ withLock: <resource>}`.
212-
* `sharedStorage.batchUpdate(methods, options)`, with the `withLock` option, allows multiple modifier methods to be executed atomically, enabling use cases where a website needs to maintain consistency while updating data across multiple storage keys.
210+
* The `navigator.locks.request()` method is available to worklet environments.
211+
* All modifier methods support the option `{withLock: <resource>}`.
212+
* The `sharedStorage.batchUpdate(methods, options)` method allows multiple modifier methods to be executed atomically, by using the `withLock` option. This enables a website to maintain consistency while updating data across multiple storage keys.
213213

214214

215215
<!-- ====================================================================== -->

microsoft-edge/web-platform/site-impacting-changes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
3030

3131
<!-- order of rows: newest version (such as "Future/TBD") at top, then greatest to smallest version # -->
3232

33-
<!-- latest = 10 most recent versions (Stable channel); as of May 14, 2024, latest Stable = 124, so the 10 most recent versions = 115 through 124+ -->
33+
<!-- latest = 10 most recent versions (Stable channel); as of Feb. 10, 2025, latest Stable = 133, so the 10 most recent versions = 124 through 133 -->
3434
##### [Latest versions](#tab/latest)
3535

3636
| Change | Stable channel | Experimentation | Additional information |
@@ -51,7 +51,7 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
5151
| Change | Stable channel | Experimentation | Additional information |
5252
| --- | --- | --- | --- |
5353
| Added support for AVIF and AV1 file formats | v121 | | Microsoft Edge now supports the AVIF and AV1 file formats, which offer better compression and higher quality images and videos. Users can enjoy faster loading times and better quality media on websites. |
54-
| Ignore modifications to `document.domain` by default | v119 | | The `document.domain` property historically could be set to relax the same-origin policy and allow subdomains from a site to interact. This behavior will be disabled by default such that setting the `document.domain` property will have no effect. For more information and workarounds, see [Microsoft Edge will disable modifying document.domain](/deployedge/edge-learnmore-origin-keyed-agent-cluster). |
54+
| Ignore modifications to `document.domain` by default | v119 | | The `document.domain` property historically could be set to relax the same-origin policy and allow subdomains from a site to interact. This behavior will be disabled by default, such that setting the `document.domain` property will have no effect. For more information and workarounds, see [Microsoft Edge will disable modifying document.domain](/deployedge/edge-learnmore-origin-keyed-agent-cluster). |
5555
| New TLS server certificate verifier | v111 (managed devices), v109 (unmanaged devices) | | No site compatibility impacts are anticipated. If you have uncommon TLS server certificate deployments, you should test in v109 to confirm there's no impact. For more information and testing guidance, see [Changes to Microsoft Edge browser TLS server certificate verification](/deployedge/microsoft-edge-security-cert-verification). |
5656
| Send CORS preflight requests for private network access | v104 | | Starting with v104, Microsoft Edge sends a CORS [preflight](https://developer.chrome.com/blog/private-network-access-preflight/) request before a page from the internet is allowed to request resources from a local network (intranet). The intranet server should respond to the preflight by providing explicit permission to access the resource. The result of this check is not yet enforced. Enforcement will begin in v111 at the earliest. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see the [Chrome Platform Status entry](https://chromestatus.com/feature/5737414355058688) and [_Chrome Developers_ blog post](https://developer.chrome.com/blog/private-network-access-preflight/#rollout-plan). Two compatibility policies are available to suppress the CORS preflight request: [InsecurePrivateNetworkRequestAllowed](/deployedge/microsoft-edge-policies#insecureprivatenetworkrequestsallowed) and [InsecurePrivateNetworkRequestAllowedForUrls](/deployedge/microsoft-edge-policies#insecureprivatenetworkrequestsallowedforurls). |
5757
| Block external protocols in sandboxed frames by default | v103 | | Blocks the use of external protocols (that interact with non-browser applications) from sandboxed iframes unless permission is explicitly granted by the `sandbox` attribute on the frame. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see the [Chrome Platform Status entry](https://chromestatus.com/feature/5680742077038592). |

0 commit comments

Comments
 (0)