Re: [WICG/webcomponents] [scoped-registries] Interaction with declarative shadow DOM (#914)

> > The aforementioned ordering issue, if it turns out that it is really needed, it looks to me like it is fatal.
> 
> I don't understand this statement. The top-down ordering is exactly what we already have. What's "fatal" about it?

@justinfagnani the main thing here is whether or not this new feature changes the existing behavior? (e.g.: order of upgrading)

I, like you, don't think it does it, but I'm not sure that's what @rniwa is saying, so I want to understand more. What he is saying is:

> The proposed solution would mean that a custom element in a declarative shadow DOM can't be upgraded until all its ancestor custom elements had been upgraded.

There are two parts of that statement:

1. It implies a change in the current behavior (today it gets upgraded when the declaration is defined - in a top-down ordering).
2. It introduces a new narrative "all its ancestor custom elements", which is not relevant today for the upgrade mechanism.

My question to @rniwa is the same, is that statement correct? can you provide an example? I don't think this feature is that disruptive, but as always, I want to understand more about his concern.

If @rniwa concerns turns out to be true, and therefore it requires a change in the current behavior (according to my description above), then I will consider this fatal, and we should get back to the drawing board.

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