Why can't we have templates, custom elements and scoped CSS without JS?
Why can't we have templates, custom elements and scoped CSS without JS?
In the meantime I would look for technology which applies server side rendering to your web components.
As I understand it (and I might not; I don’t have servers to do SSR) people want SSR for two reasons. a) To allow users that don’t have JavaScript for some reason to at get good UX, and b) to prevent the styles from kicking in after the initial render. There are ways to author your components in a way that fixes (b), but I’m not aware of any technique other then SSR that will fix (a).
For things that aren't web apps, like blog/wiki/docs/news-site the primary content is text + images + links.
Is it not attractive to avoid JS where not needed? And only use it for the tiny bits that really do need it.
DSD is already shipping in Chrome 90 and Edge 91. I suspect that will put pressure on others to either adopt or continue with the standardization process until it addresses their outstanding concerns.
* Custom Elements
* Shadow DOM (seems to be optional in practice)
* HTML Template Elements
* ES Modules (formerly HTML Imports)
When compared with React and similar solutions doing the same and similar thing(s) it runs circles around them... or am I misunderstanding the comment and is the position asserted that container queries (not web components) are the effect?
What is the inner-platform effect comment applied to specifically?
Adding more flexibility to CSS/HTML without requiring Javascript would eventually turn CSS and HTML into to the equivalent of a general purpose programming language, which we already have in the form of Javascript.