Merge pull request #4933 from MicrosoftDocs/main

add 130 issue - non-special scheme URL handling

edgeenterprise/microsoft-edge-known-issues.md

@@ -3,7 +3,7 @@ title: "Microsoft Edge known issues"
 ms.author: archandr
 author: dan-wesley
 manager: likuba
-ms.date: 10/24/2024
+ms.date: 10/28/2024
 audience: ITPro
 ms.topic: conceptual
 ms.service: microsoft-edge
@@ -26,6 +26,7 @@ The following table lists the issues that the Microsoft Edge team is tracking cl
 ----->
 |  Version  | Symptom | Workaround | Comment |
 | --- | --- | --- | --- |
+| 130 | In Microsoft Edge Stable Version 130.0.2849.46, non-special scheme URL handling was updated to become compliant with the URL Standard ([https://url.spec.whatwg.org/](https://url.spec.whatwg.org/)). This change has site compatibility impacts which may require changes to your web sites. For more information and web developer guidance, see [http://bit.ly/url-non-special](http://bit.ly/url-non-special). | Ensure your clients receive configuration payloads by either not configuring the [ExperimentationAndConfigurationServiceControl](/deployedge/microsoft-edge-policies#experimentationandconfigurationservicecontrol) policy or setting the policy to "FullMode" or "ConfigurationsOnlyMode". Alternatively, roll back to Microsoft Edge to version 129.0.2792.89. |  Recognizing the broad impact this issue is having, Microsoft decided to temporarily disable this feature through the [Experimentation and Configuration Service (ECS)](/deployedge/edge-configuration-and-experiments). This feature disablement is now fully rolled out to Edge 130 Stable (100%), so it is expected that this will take effect after a browser restart.<br><br>In addition, and [if ECS is disabled through policy](/deployedge/microsoft-edge-policies#experimentationandconfigurationservicecontrol), a code change to temporarily disable this feature is being checked in, which will be included in an upcoming Edge 130 Stable release. An update will be provided once Microsoft determines which Edge stable release will address the issue.<br><br>**Note:** This feature is planned to be turned on again in Microsoft Edge version 133. Admins can use the *StandardCompliantNonSpecialSchemeURLParsing* feature flag to explicitly enable the feature in the [Edge Canary Channel](https://www.microsoft.com/en-us/edge/download/insider?msockid=3d18d32cb9d96ec733a3c7b1b8636f96&form=MA13FJ). Customers are encouraged to test the impact of this upcoming feature and prepare for the change in behavior.|
 | 130 | Starting with Microsoft Edge Stable version 130.0.2849.46, some browser extensions are no longer working if they are using the chrome.storage.managed API. | Roll back Microsoft Edge to version 129.0.2792.89. | This issue is fixed in Microsoft Edge stable release 130.0.2849.56. |
 | 128    | Starting with Microsoft Edge Stable version 128.0.2739.42, pages may fail to fully load when retrieving resources from the HTTP cache. When the issue is encountered, DevTools shows the requests failing with net::ERR_FAILED.| Roll back Microsoft Edge to version 127.0.2651.105 for Edge Stable or version 126.0.2592.137 for Edge Extended Stable.<br><br>A force reload (Ctrl+Reload button) can mitigate individual page loads.<br><br>Site owners may also consider reducing the use of HTTP caching for impacted resources until the issue is addressed. |Microsoft is collaborating with the Chromium project via [Chromium bug 362788339]( https://issues.chromium.org/issues/362788339) to address the issue. This issue is fixed in Microsoft Edge stable release 128.0.2739.63. |
 | 128    | Starting with Microsoft Edge Stable version 128.0.2739.42, custom configured start pages appear to be stuck in the loading state. | Roll back Microsoft Edge to version 127.0.2651.105 for Edge Stable or version 126.0.2592.137 for Edge Extended Stable.<br><br>Use the command line argument: `"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features="msIrm, msIrmv2, msEndpointDLp"`<br>**Note:** Command line args are case sensitive. | The fix is included in Stable version 128.0.2739.54.  |