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

@bathos yes, please don't take my naming suggestions as actual suggestions, it's the concept that matters, I don't have opinion for names except it should be not ambiguous, so both your hints would be more than welcome to me.

@keithamus like I've said, this was a workaround from 5+ years ago, when I've already raised the concerns around V1 dropping the `createdCallback` https://github.com/WebReflection/html-parsed-element#readme

As a matter of fact, it uses indeed a combination of everything you mentioned already, see [the source code](https://github.com/WebReflection/html-parsed-element/blob/master/esm/index.js) but it's still a hell of a hack or workaround nobody should or would need if the platform would provide the same.

The current status is that if more than a custom in-house solution lands on pages we have slower pages for everyone and nobody wins + all sorkarounds are heavier and slower by design but also error prone.

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

Message ID: <WICG/webcomponents/issues/809/1463780582@github.com>