- From: Douglas Parker <notifications@github.com>
- Date: Tue, 07 Mar 2023 22:47:51 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 8 March 2023 06:48:04 UTC
Not to add too much noise here, but if the consensus is that this _cannot_ be parser specific then I just want to point out hydration as a motivating use case (which I don't see in this thread?) I think there is a lot of value in being able to write "when this component is fully parsed, hydrate it". That inherently needs to be a parser feature, since hydration would be unrelated to any mutations applied to the element mid-parse. This is especially important for streaming use cases and is technically necessary anytime you hydrate a component defined in an async script tag, since it may execute while the document is mid-parse of a hydratable element. I just wanted to point out hydration as one use case which would really benefit from a parser notification here and I don't think any non-parser approach like `MutationOberserver` meets that need. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/809#issuecomment-1459624868 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/809/1459624868@github.com>
Received on Wednesday, 8 March 2023 06:48:04 UTC