Re: [whatwg/dom] Allow elements with a null customElementRegistry without Shadow DOM (Issue #1413)

sorvell left a comment (whatwg/dom#1413)

> Is that a more common pattern comparing to scenario where we want to keep the registry null?

I believe there are no common patterns here. This new behavior. The backwards compatibility issue with a null registry is related only to adopting from another document and is specifically relevant for templates. This is why [I suggested](https://github.com/whatwg/dom/issues/1413#issuecomment-3394909008) just doing the null switch on adopting and not insertion.

> If we all agree that we’re open to an attribute for element to leave its registry null like how declarative shadow root works, I’m leaning more towards keeping the current behavior in spec for insertion 

I really see no reason to treat an element with a null registry as somehow special and needing to have its registry changed on insertion. We have `initialize` specifically for giving an element a registry. Currently there is no way to have an element with a null registry in the main DOM tree which is [problematic for registry users](https://github.com/whatwg/dom/issues/1413#issuecomment-3393342472) that don't want to use Shadow DOM. Relying on an as yet unspecified global element attribute for this behavior is unsatisfying. There may be issues with it, and I just don't see a good reason to block fundamentally useful behavior on that.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1413#issuecomment-3470767161
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1413/3470767161@github.com>