- From: Mason Freed <notifications@github.com>
- Date: Fri, 15 Dec 2023 09:43:18 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 15 December 2023 17:43:24 UTC
> @mfreed7 I don't really understand the `script` use case. That seems like some kind of meta-programming it wasn't designed for. I think Opera at some point had `beforeexecute` events and such, but they had their own issues. > > If it's for rendering I'd expect you maybe delay a bit and then just render what you have at some interval. Similar to incremental rendering in browsers. The use case (one of them, at least) is waiting for `<script>` tags to finish parsing (and therefore contain all of the script) and then moving the script element between documents. If there's no way to know when all of the script is there, it's brittle. I'm not sure we have a list of the use cases the web is "designed for". We provide functionality, and creative developers build cool things with that functionality. Parsing `<script>`s and moving them between documents is certainly one part of that functionality that seems like fair game. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/809#issuecomment-1858249199 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/809/1858249199@github.com>
Received on Friday, 15 December 2023 17:43:24 UTC