Joe Pea

That's a good question! I normally just go by screen size for responsiveness, but a desktop user could definitely have a touch screen. Maybe, if the size is desktop, start...

@ryansolid what are your thoughts on the syntax proposed in the OP, which would allow explicit control over this no matter what element a boolean attribute is being used on?...

I forgot to mention, that explicit values can currently be achieved with `attr:`, f.e. `` or `` should always work for the above use case. The key here is that...

The solution seems to be that the upgrade process should set the root's `available to element internals` to `true` before running a custom element constructor, as the custom element constructor...

Why is a ShadowRoot `available to element internals` state even needed? It is not possible to get `ElementInternals` before upgrade right? For example, calling `attachInternals` like this throws: ```html customElements.define(...

It was introduced to prevent someone defining an non-defined custom element (element with dash in the name) later, and getting access to a closed `ShadowRoot`. That's not worth the problems...

There's one more issue that needs to be addressed for DSD to be useful for everyone: both the element tag name, and the template, should be parsed together: Example 1:...

@sorvell mentioned that to maintain BC, I think we will likely need something like: ```js parsingCompleteCallback() { if (!this.#internals.shadowRoot) { this.attachShadow(...); } } ``` but this means it requires JavaScript....

(content deleted, need to think about this more to provide a concise explainer with solution ideas)

@annevk > You are combining too many things in a single issue. That may be because you haven't taken the time to understand the problem. Everything I mentioned above is,...