Re: [w3c/webcomponents] components v1 native implementation - inner components problem (#615)

You might need a different callback,  (imagine something like "`parserPoppedEndTag`"), to do what you want. Custom elements do not have that callback but the group could consider adding it.

I have heard from other authors that a callback at this time would be useful; the use case is to delay initialization work that would be invalidated by markup children (like OBJECT/PARAM.) You still have to use MutationObservers to track DOM changes; this use case is for performance optimization.

Depending on the timing of the callback it might also simplify when to start listening to mutation events (because today you get no clear signal whether your constructor was invoked for upgrade, and you should process existing children, or not. This callback could be an opportunity to put that code in one place.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/615#issuecomment-314638044