- From: Mason Freed <notifications@github.com>
- Date: Thu, 28 Mar 2024 09:11:47 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 March 2024 16:11:50 UTC
> 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. Another use case (for builtin elements) is [source selection for `<video>`](https://github.com/whatwg/html/issues/10077#issuecomment-1999397959). The conclusion on that issue seems to be that the best behavior is indeed to wait for the end tag before making a source selection. If that conclusion sticks, it'll be another instance of something a built-in element can do that a custom element cannot, because of the lack of the API this issue proposes. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/809#issuecomment-2025591347 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/809/2025591347@github.com>
Received on Thursday, 28 March 2024 16:11:50 UTC