https://github.com/horo-t/explainers/blob/main/script_element_supports.md
https://html.spec.whatwg.org/multipage/scripting.html#dom-script-supports
Provides a unified way to detect new features that use script elements.
https://github.com/w3ctag/design-reviews/issues/674
Pending
This method provides a synchronous way of feature detections. But for unsupported browsers, developers need to use an asynchronous way as discussed at https://github.com/WICG/import-maps/issues/171.
Gecko: Worth prototyping (https://github.com/mozilla/standards-positions/issues/576)
WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-September/031979.html)
Web developers: Positive The developer feedback on the spec issue (https://github.com/whatwg/html/issues/6472) was positive.
No known ergonomics risks.
No known activation risks. This method is easy to use.
No known security risks.
None.
Developers can call this method from DevTools's console.
Yes
Yes
https://github.com/horo-t/explainers/blob/main/script_element_supports_how_to.md
ScriptElementSupports
False
https://bugs.chromium.org/p/chromium/issues/detail?id=1245528
DevTrial on desktop 95
DevTrial on Android 95
DevTrial on Webview 95
https://www.chromestatus.com/feature/5712146835963904
Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/evk2qgsekYk/m/WtdE_XplBQAJ
This intent message was generated by Chrome Platform Status.