Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)

Ok, this is great @rniwa, that clarifies a lot. My intution here is as follow:

1. Today, with the global registry, this example will upgrade 6 elements in the following order:

```
SomeElement with id=d2s1
SomeElement with id=d1s1
SomeElement with id=d1s2
OtherElement inside SomeElement with id=d2s1
OtherElement inside SomeElement with id=d1s1
OtherElement inside SomeElement with id=d1s2
```

with `SomeElement` with `id=d3s1` being the only one that is never upgraded since it was inserted inside the iframe.

2. Tomorrow, with the scoped registry, this example will still only 4 elements, in the following order:

```
SomeElement with id=d2s1
SomeElement with id=d1s1
SomeElement with id=d1s2
SomeElement with id=d3s1 (because it is defined in the scoped registry for `d3`)
```

While `OtherElement` instances are never upgraded because all div's shadow roots are using scoped registries.

I believe your concrete question is about `d3s1`, and whether or not it should be upgraded due to the fact that it is defined in a scoped registry from the outer window, which is plugged into the iframe while appending the div. But I don't see a reason why not, considering that we don't inherit or use the global registry when a scoped registry is used. Do you see any reason for a scoped registry to not be used by shadow roots attached to elements from different documents?

-- 
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/716#issuecomment-680516883