- From: Kouhei Ueno via GitHub <sysbot+gh@w3.org>
- Date: Sat, 08 Apr 2017 06:46:11 +0000
- To: public-houdini-archive@w3.org
>From implemetor + spec reader POV, using `<script>` element implies that the worklets are going to be a variation of [script](https://html.spec.whatwg.org/multipage/webappapis.html#concept-script) and scheduled via [script processing model](https://html.spec.whatwg.org/multipage/scripting.html#script-processing-model).
I share the concern w/ @domenic here that having a script variation that doesn't run in the main world environment may be a bit complicated. I'm also not completely sure what {async,defer} would mean for worklet scripts. @domenic's proposal of using `<link>` element is much easier to implement in terms of current Blink.
However, from pure mark-up perspective, I can also be convinced that `<script>` is the most natural way to express any kind of script fragment in the code. Implementing the primitive in Blink isn't technically impossible, but as we are currently actively rationalizing the existing code to actually implement script concept as specified and adding module script concept, it will take some time to deliver.
--
GitHub Notification of comment by nyaxt
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/376#issuecomment-292699344 using your GitHub account
Received on Saturday, 8 April 2017 06:46:17 UTC