Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784)

@daKmoR 
Thanks a lot for your input.

> <div is="built-in"> you can't really find in the wild as it's mostly discouraged for the fact that safari is not going to implement it => so maybe just remove it?

Indeed that's true, unfortunately Safari refuses to implement it. Though extended built-in elements are living standard and the majority supports it. Hence this diagram should reflect the standard, though an `*` asterisk with mentions below would make sense.

> I'm not sure what the --> x at `attributeChangedCallback`, `connectedCallback`, `adoptedCallback` and custom properties means.

So the spec has still glitches, the behavior of these callbacks are not 100% deterministic.
The `--> x` shall show that there maybe glitch-checks needed.
For more info see this test page please:
https://wc-connected-test.glitch.me/

Also the spec itself notes about `connectedCallback` glitches like:

> An element's `connectedCallback` can be queued before the element is disconnected, but as the callback queue is still processed, it results in a `connectedCallback` for an element that is no longer connected:
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-element-conformance

> for custom properties I'm also not sure what does it mean in general in this context?

Okay, so every custom observed HTML attribute should have a corresponding DOM property.
More info: https://developers.google.com/web/fundamentals/web-components/best-practices#attributes-properties


-- 
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/784#issuecomment-457857302