Skip to content

Commit 2dd965a

Browse files
mikehoffmsmikehoffms
committed
inc rvw
1 parent 64ac9bd commit 2dd965a

3 files changed

Lines changed: 13 additions & 30 deletions

File tree

‎microsoft-edge/extensions-chromium/developer-guide/run-compiled-code.md‎

Lines changed: 5 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -18,13 +18,13 @@ See:
1818

1919

2020
<!-- ====================================================================== -->
21-
## Native Client (NaCl) (deprecated)
22-
<!-- sections that point to here:
23-
* [Deprecation of Native Client (NaCl)](../whats-new/roadmap.md#deprecation-of-native-client-nacl) in _Roadmap for Microsoft Edge Add-ons_.
24-
* "Native Client (NaCl)" table row in [Latest versions](../../web-platform/site-impacting-changes?tabs=latest#high-impact-changes) in _Site compatibility-impacting changes coming to Microsoft Edge_.
21+
## Native Client (NaCl) no longer supported
22+
<!-- sections that point to this article because of this section:
23+
* [Native Client (NaCl) no longer supported](../whats-new/roadmap.md#native-client-nacl-no-longer-supported) in _Roadmap for Microsoft Edge Add-ons_.
24+
* "Removal of Native Client (NaCl)" table row in [Earlier versions](../../web-platform/site-impacting-changes?tabs=earlier#high-impact-changes) in _Site compatibility-impacting changes coming to Microsoft Edge_.
2525
-->
2626

27-
To enhance web security and performance, Native Client (NaCl) is deprecated for Microsoft Edge, along with other browsers. NaCl was deprecated (discouraged but still supported) starting in 2020. Support for NaCl will be discontinued starting with Microsoft Edge 138.
27+
To enhance web security and performance, Native Client (NaCl) is no longer supported by Microsoft Edge (along with other browsers). Native Client (NaCl) was supported through Edge version 115. In 116 to 119, NaCl was only usable by enabling an enterprise policy. Starting with 120 (December 2023), support for NaCl was completely removed.
2828

2929
NaCl is a sandbox for running compiled C and C++ code in browsers efficiently and securely, independently of the user's operating system. WebAssembly (Wasm) is recommended instead of NaCl.
3030

@@ -36,20 +36,3 @@ To Run compiled code in an extension, we recommend using WebAssembly instead of
3636
* [WebAssembly Migration Guide](https://developer.chrome.com/docs/native-client/migration) in Chrome docs.
3737
* [WebAssembly](https://developer.mozilla.org/docs/WebAssembly) at MDN.
3838
* [webassembly.org](https://webassembly.org)
39-
40-
41-
<!-- ====================================================================== -->
42-
<!-- ## See also -->
43-
<!-- all links in article -->
44-
<!-- up to date 2025/02/06 but commented out b/c not needed unless article is longer -->
45-
46-
<!--
47-
WebAssembly (Wasm):
48-
* [WebAssembly](https://developer.mozilla.org/docs/WebAssembly) at MDN.
49-
* [WebAssembly Migration Guide](https://developer.chrome.com/docs/native-client/migration) in Chrome docs.
50-
* [webassembly.org](https://webassembly.org)
51-
52-
Native Client (NaCl):
53-
* [Manifest - Nacl Modules](https://developer.chrome.com/docs/extensions/mv2/manifest/nacl-modules) in Chrome docs.
54-
* [Native Client](https://developer.chrome.com/docs/native-client) - deprecation notice for Chrome browser.
55-
-->

‎microsoft-edge/extensions-chromium/whats-new/roadmap.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
66
ms.topic: conceptual
77
ms.service: microsoft-edge
88
ms.subservice: extensions
9-
ms.date: 02/10/2025
9+
ms.date: 02/14/2025
1010
---
1111
# Roadmap for Microsoft Edge Add-ons
1212
<!-- https://aka.ms/EdgeAddonsRoadmap -->
@@ -15,19 +15,19 @@ These are the next planned [Partner Center](https://partner.microsoft.com/dashbo
1515

1616

1717
<!-- ====================================================================== -->
18-
## Deprecation of Native Client (NaCl)
18+
## Deprecation of the Update REST API v1
1919

20-
To enhance web security and performance, Native Client (NaCl) is deprecated for Microsoft Edge, along with other browsers. WebAssembly (Wasm) is recommended instead of NaCl.
20+
As of September 6, 2024, both v1.1 and v1 of the Update REST API are supported. Support for v1 will end on December 31, 2024.
2121

22-
See [Native Client (NaCl) (deprecated)](../developer-guide/run-compiled-code.md#native-client-nacl-deprecated) in _Run compiled code in an extension_.
22+
See [Using the REST API for updating Microsoft Edge Add-ons](../publish/api/using-addons-api.md).
2323

2424

2525
<!-- ====================================================================== -->
26-
## Deprecation of the Update REST API v1
26+
## Native Client (NaCl) no longer supported
2727

28-
As of September 6, 2024, both v1.1 and v1 of the Update REST API are supported. Support for v1 will end on December 31, 2024.
28+
Native Client (NaCl) was supported through Edge version 115. In 116 to 119, NaCl was only usable by enabling an enterprise policy. Starting with 120 (December 2023), support for NaCl was completely removed.
2929

30-
See [Using the REST API for updating Microsoft Edge Add-ons](../publish/api/using-addons-api.md).
30+
To enhance web security and performance, Native Client (NaCl) is no longer supported by Microsoft Edge (along with other browsers). WebAssembly (Wasm) is recommended instead of NaCl; see [Run compiled code in an extension](../developer-guide/run-compiled-code.md).
3131

3232

3333
<!-- ====================================================================== -->

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,6 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
3838
| Insecure downloads over HTTP | Future release (TBD) | | When a user tries to download potentially dangerous content from an HTTP site, the user will receive a UI warning, such as "Insecure download blocked." The user will still have an option to proceed and download the item. Admins can use the `InsecureContentAllowedForUrls` policy to specify HTTP sites for which the warning will be suppressed. Admins can use the `InsecureDownloadWarnings` feature flag to test the impact of this upcoming feature. |
3939
| Deprecate unload event | Future release (TBD) | | Introduces a new Permission-Policy to allow creating unload event listeners. The default policy is `allow`, but the default policy will gradually be migrated to `deny`, such that unload handlers stop firing on pages, unless a page explicitly opts in to re-enable them. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see [Intent to Deprecate: Deprecate unload event](https://groups.google.com/a/chromium.org/g/blink-dev/c/dvusqw9-IhI/m/SBkm_u1RAQAJ). |
4040
| Removal of cross-origin subframe JavaScript dialogs | Future release (TBD) | | Removes `window.alert`, `window.prompt`, and `window.confirm` from cross-origin iframes. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see [Intent to Remove: Cross origin subframe JS Dialogs](https://groups.google.com/a/chromium.org/g/blink-dev/c/hTOXiBj3D6A/m/JtkdpDd1BAAJ). |
41-
| Removal of Native Client (NaCl) | v138 | | To enhance web security and performance, Native Client (NaCl) is deprecated for Microsoft Edge, along with other browsers. NaCl was deprecated (discouraged but still supported) starting in 2020. WebAssembly (Wasm) is recommended instead of NaCl. See [Native Client (NaCl) (deprecated)](../extensions-chromium/developer-guide/run-compiled-code.md#native-client-nacl-deprecated) in _Run compiled code in an extension_. |
4241
| WebGPU `maxInterStageShaderComponents` limit | v133 | | The WebGPU `maxInterStageShaderComponents` limit is being removed. See [Deprecate WebGPU limit maxInterStageShaderComponents](./release-notes/133.md#deprecate-webgpu-limit-maxinterstageshadercomponents). |
4342
| `<link rel=prefetch>` five-minute rule | v133 | | Previously, when a resource was prefetched by using `<link rel=prefetch>`, its cache semantics (specifically, `max-age` and `no-cache`) were ignored for the first use within 5 minutes, to avoid refetching. Now, this special case has been removed, and normal HTTP cache semantics are used. See [Remove `<link rel=prefetch>` five-minute rule](./release-notes/133.md#remove-link-relprefetch-five-minute-rule). |
4443
| Deprecate `textprediction` attribute | v133 | | Removes support for the `textprediction` HTML attribute, which is a nonstandard attribute that's used to enable or disable the browser-based Text Prediction feature for long-form text inputs. Instead, use the standardized `writingsuggestions` attribute, which functions similarly to `textprediction`, but also applies to other writing-assistance features that browsers may provide. Sites that explicitly set `textprediction` to `true` or `false` can instead set `writingsuggestions` to the same value. For more information, see [Writing suggestions](https://html.spec.whatwg.org/multipage/interaction.html#writing-suggestions) in the HTML specification. |
@@ -52,6 +51,7 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
5251
| Change | Stable channel | Experimentation | Additional information |
5352
| --- | --- | --- | --- |
5453
| 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+
| Removal of Native Client (NaCl) | v120 | | To enhance web security and performance, Native Client (NaCl) is no longer supported for Microsoft Edge (along with other browsers). NaCl was supported through v115. In v116 through v119, NaCl was only usable by enabling an enterprise policy. WebAssembly (Wasm) is recommended instead of NaCl; see [Run compiled code in an extension](../extensions-chromium/developer-guide/run-compiled-code.md). |
5555
| 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). |
5656
| 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). |
5757
| 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). |

0 commit comments

Comments
 (0)