Re: [w3c/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)

> Much of this thread and previous ones is a discussion about how custom elements which have this sort of behavior are discouraged, and so adding an API to make them easier is not desirable for some of us.
> 
> I imagine you might be aware of that, but in case others are coming in via Twitter or similar, I thought it'd be good to re-establish that context.

@domenic Thanks for thinking of people me which landed on this thread without any context.
Can you please share the rationale behind this decision (to discourage such behaviour) or a link to it?

I was going to add my 2 cents, but perhaps knowing the history, will help answer some (of my) questions and avoid the conversation repeating itself. Thanks.

-- 
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/809#issuecomment-534102718