17112 2012-05-18 20:05:58 +0000 [Custom]: Specify behavior of <script> element when child of <element> 2012-08-24 23:38:59 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 17103 1 dglazkov dglazkov dominicc public-webapps-bugzilla oldest_to_newest 67909 0 dglazkov 2012-05-18 20:05:58 +0000 The fact that <script> element behaves differently when it is a child of <element> is bothersome. What are the alternatives? 67996 1 dominicc 2012-05-22 06:44:39 +0000 Templates have already made a decision on this: <https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#definitions> Namely that <script> is inert; so be it. If there is an applicable alternative it should be examined for use in the template case as well. 68011 2 dglazkov 2012-05-22 16:10:26 +0000 (In reply to comment #1) > Templates have already made a decision on this: > > <https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#definitions> > > Namely that <script> is inert; so be it. If there is an applicable alternative > it should be examined for use in the template case as well. This is for when <script> is a child of <element>, not <template>. It is not inert, but is instead executed in a specially constructed scope. 68028 3 dominicc 2012-05-23 04:58:21 +0000 Got it. If you want to run the script in a different context, I don’t see how you get around having different semantics. For example you could do <element onmumble="f()"> and fire onmumble after the child script has run. But then that script is running in the typical window context to define f. 72746 4 dglazkov 2012-08-24 23:38:59 +0000 http://dvcs.w3.org/hg/webcomponents/rev/15fded36e9c9