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

> Now browsers that don't support DSD (which is currently all of them) will see none of the content on SSR render. (yes there is the `if (!this.shadowRoot) { // gen dom }` option but that is liable to CLS and only works on [browsers with WC support](https://caniuse.com/custom-elementsv1)).

I don't think considering ancient browsers is really a strong consideration for a feature that simply adds a declarative version of something that ancient browsers don't support anyway.

If your tool already supports Shadow DOM then it shouldn't be too difficult to extend it to declarative shadow DOM, as all the same logic applies.

Also regarding old browser support, if they're actually a large part of your users, WC is probably not the easiest choice for building your site (this is not exclusive to web components, many new things will require heavy tooling and won't work in all cases, e.g. CSS grid).

As a general rule regarding old browsers you should probably consider 3 cases:

1. They're a large/signicantly valuable part of your user base. In this case you should probably avoid most new technologies that are not trivially polyfillable.
2. They're a minority. In this case you should probably just provide a functional but downgraded experience, for example don't worry about things like flash of unstyled content, slightly broken CSS or other things. As long as core things work this is fine.
3. They're a trivial minority, or you need technology fundamentally incompatible with older browsers (e.g. apps that use Web Audio). In this case you can't really do a lot, just encourage them to upgrade their browser if they really want to access it.

-- 
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/831#issuecomment-770293178