You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Don't set document.currentScript for <script type="module"> #997
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.
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.
@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 document.currentScript and manipulate it before it gets executed. The events are also controversial per #943 so only Gecko would implement support for them presumably...
Activity
smaug---- commentedon Apr 5, 2016
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.
domenic commentedon Apr 5, 2016
beforescriptexecute and afterscriptexecute, you mean? They seem somewhat unrelated to me... modules would still have them.
smaug---- commentedon Apr 5, 2016
Don't know why those are unrelated, but anyhow, something to keep in mind at least.
Don't update document.currentScript for module scripts
annevk commentedon Apr 6, 2016
@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
document.currentScriptand manipulate it before it gets executed. The events are also controversial per #943 so only Gecko would implement support for them presumably...Make module scripts modify less global script state
Make module scripts modify less global script state
Make module scripts modify less global script state
Don't update document.currentScript for module scripts