*Contact emails* [email protected] *Explainer* https://gist.github.com/yoavweiss/a54501545ab2ad22bfde0ebed02a115c
*Specification* https://github.com/whatwg/html/pull/10327 *Summary* Currently web developers cannot retry failed module loads, as these failures are being cached (and retries just result in immediate failures). This change to the module loading behavior enables failed module loads to be manually retried (e.g. by calling `import()` again), solving real developer (and user) pain when it comes to using modules over unstable networks. *Blink component* Blink>HTML>Modules <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EHTML%3EModules%22> *Web Feature ID* Missing feature - filed https://github.com/web-platform-dx/web-features/issues/4335 *Motivation* This change enables developers to retry failed module loads (e.g. due to network failures). *Initial public proposal* https://github.com/whatwg/html/pull/10327 *TAG review* *N/A - This minor behavior change landed in HTML and shipped (ToT) by both Gecko and WebKit.* *TAG review status* Not applicable *Goals for experimentation* None *Risks* *Interoperability and Compatibility* *This change is positive from an interop perspective, as it aligns to what Gecko and WebKit have implemented and shipped.*I don't believe it carries a big risk from a compat perspective, as developers are unlikely to rely on the fact that past-failed module fetches will continue to fail in the future. *Gecko*: Shipped/Shipping ( https://bugzilla.mozilla.org/show_bug.cgi?id=2055211) *WebKit*: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=319492) *Web developers*: Strongly positive The issue was originally opened by developers and the spec change was driven by them. Multiple different teams at Shopify are hitting the issues that this is solving. I'm pretty confident that this is a common issue for module-using developers at large. *Other signals*: *WebView application risks* Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? *No information provided* *Debuggability* *No information provided* *Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?* Yes *Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* Yes https://wpt.fyi/results/html/semantics/scripting-1/the-script-element/module/dynamic-import/repeated-imports.any.html?label=experimental&label=master&aligned https://wpt.fyi/results/html/semantics/scripting-1/the-script-element/json-module/repeated-imports.any.html?label=experimental&label=master&aligned *Flag name on about://flags* *No information provided* *Finch feature name* ModuleMapDoNotCacheFailedFetch *Rollout plan* Will ship enabled for all users *Requires code in //chrome?* False *Tracking bug* https://issues.chromium.org/issues/534781954 *Estimated milestones* Shipping on desktop 154 Shipping on Android 154 Shipping on WebView 154 *Anticipated spec changes* Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). *No information provided* *Link to entry on the Chrome Platform Status* https://chromestatus.com/feature/5214647044145152?gate=6129672218869760 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohS%2ByokAFhVf66miVAqGqqO7Scps2GwrfqH3AO%2B0N72_Qeg%40mail.gmail.com.
