-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't set document.currentScript for <script type="module"> #997
Comments
How should the relevant events work in this case. For shadow DOM we can mark the events scoped, but that doesn't really affect to the behavior in light DOM. |
beforescriptexecute and afterscriptexecute, you mean? They seem somewhat unrelated to me... modules would still have them. |
Don't know why those are unrelated, but anyhow, something to keep in mind at least. |
@domenic I think we should not dispatch those either. I think the idea with those events is that you can then grab the script (using |
Per discussions in web components F2F, we don't like this API anymore and want to consider a better one for new stuff like modules and scripts-inside-shadow-DOM.
/cc @jonco3 @ajklein @Constellation @DigiTec
The text was updated successfully, but these errors were encountered: