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
The script in the template is inert, and should run when the template is inserted as ShadowDOM into any <x-cheese> element. However, this only occurs when the elements are declared inline; when the elements are imported via <link rel="import">, the inert script does not get activated.
I'm not sure this is really going to be supported. There is after all an elaborate mechanism for attaching code to the instancing of a custom element (which has evolved to avoid all kinds of messy problems). In any case, if it doesn't work under native ShadowDOM and you think it should, you may have to file a bug here: https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14978
This is due to the way HTMLImports is polyfilled. Imports are retrieved, a new document is made, and the html for that document is set via innerHTML. For security reasons, script nodes generated in this way do not execute. The native implementation of HTMLImports should run these scripts.
Unless there's a compelling reason, we do not plan to correct this behavior.
When you have an element like this
The script in the template is inert, and should run when the template is inserted as ShadowDOM into any
<x-cheese>
element. However, this only occurs when the elements are declared inline; when the elements are imported via<link rel="import">
, the inert script does not get activated.Browser: Chromium 28.0.1496.0 (Developer Build 197749)
OS: Linux
Blink: 537.36 (Unknown URL@0)
JavaScript: V8 3.18.5.2
Experimental features enabled (e.g. native ShadowDOM, etc)
The text was updated successfully, but these errors were encountered: