- From: Ryosuke Niwa <notifications@github.com>
- Date: Mon, 06 Mar 2023 13:36:14 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 March 2023 21:36:26 UTC
> > Ok what about the second simple straightforward solution? > > For this and all of the similar questions, the answer is because they all fail in this case: > > ``` > <my-element> > ...Lots of content here... > > {... the HTML parser yields here, renders the document, and spins the event loop. > All workarounds above fire here.} > > ...More content here, which are still children of <my-element> > </my-element> > ``` On the other hand. maybe whatever code which will run once all child nodes are parsed should be running whenever parser yields like that as well. Maybe we can make this callback be called in those cases with a boolean argument indicating the state: class MyElement extends HTMLElement { ... didParseChildren(bool didFinish) { // didFinish will be false when this is getting called due to parser yields. } ... } -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/809#issuecomment-1457036657 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/809/1457036657@github.com>
Received on Monday, 6 March 2023 21:36:26 UTC