Re: [whatwg/dom] Declarative Shadow DOM (#510)

I don't think we all realize the implications of this decision. Yes, there are many hacks that we can do, but each of them will have implications and limitations.

The main situation here is that without a proper mechanism to process a fully consumable HTML that can "eventually" be upgraded by registering the components will put WC in a very precarious position with respect to all other frameworks, and will be a deal breaker for many to not only avoid writing Web Components, but to avoid use/consuming Web Components, which is the most concerning part of it for me.

Here is my bucket list:

* I want it to produce HTML files that are indexable by search engines first and foremost.
* I want my HTML to show consumable content immediately (scripts/modules are deferred because that's how we roll these days).
* I want to encapsulate styles for the different parts of my HTML.
* I want to upgrade parts of my HTML to enhance them so they become interactive.
* I want my HTML to be resilience even when rolling with slow or flaky networks.
* ... I also want a pony!

@justinfagnani's suggestion falls short on multiple items from that list, and I must say that his example is the most compelling solutions that I have seen so far, but unfortunately it's just not good enough.

I did not make it to the meeting, but I will like to get more details about the compromise around `<template>` with `shadowroot` attribute. It sounds like a good compromise, and users' confusion does not hold any water here, users are already confused with `<template>` in general.

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