Skip to content

Commit a912002

Browse files
Merge pull request #3160 from MicrosoftDocs/user/mikehoffms/site-compat
Add row "Insecure downloads over HTTP" in "Site compatibility-impacting changes"
2 parents f9dc5e4 + 0795bab commit a912002

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: MSEdgeTeam
55
ms.author: msedgedevrel
66
ms.topic: conceptual
77
ms.service: microsoft-edge
8-
ms.date: 04/05/2024
8+
ms.date: 05/15/2024
99
---
1010
# Site compatibility-impacting changes coming to Microsoft Edge
1111

@@ -30,11 +30,12 @@ This table lists:
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 Apr. 5, 2024, latest Stable = 123, so the 10 most recent versions = 114 through 123+ -->
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+ -->
3434
##### [Latest versions](#tab/latest)
3535

3636
| Change | Stable channel | Experimentation | Additional information |
3737
| --- | --- | --- | --- |
38+
| 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. |
3839
| 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). |
3940
| 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). |
4041
| Deprecate `textprediction` attribute | v131 | | 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. |
@@ -43,6 +44,7 @@ This table lists:
4344
| 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. |
4445
| 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). |
4546

47+
4648
##### [Earlier versions](#tab/earlier)
4749

4850
| Change | Stable channel | Experimentation | Additional information |

0 commit comments

Comments
 (0)