Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)

> So - just to check in with implementers (and specifically @emilio, @mfreed7, @rniwa who were in the meeting and may recall the discussion, also /cc @smaug---- for more confirmation on the Gecko side) - could we always populate the `TreeScope` with a Node subtype or Node instance which has a new bit set to say "this is a dummy proxy Node that points to a parent but shouldn't be given to script, and is just for keeping the shadowroot reference alive so that createElement & co work seamlessly" (the variable name could use some bikeshedding).

I'm supportive of an approach like this to allow us to keep track of the link to follow to find the correct (scoped) registry. One nit might be that I was thinking you'd put a bit on `Element` that means "my TreeScope reference isn't real - I'm disconnected. But the TreeScope reference *does* point to a TreeScope that has a registry that you can use for element creation". That's maybe what you meant by that paragraph, but I just wanted to make sure. But that's really in the details - I'm supportive.

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

Message ID: <WICG/webcomponents/issues/1078/2415239141@github.com>