2 ms·
You won't be able to do that in the forseeable future. Multiple reasons why: - Rich Harris (author of Svelte): eager (when laziness is preferable), styling is
by dmitriid 7y ago
You won't be able to do that in the forseeable future.
Multiple reasons why:
- Rich Harris (author of Svelte): eager (when laziness is preferable), styling is problematic, add confusion to attributes vs. props with disastrous ergonomics, leaky design, bad underlying model (DOM), global namespace [1]
- Serhii Kulykov (building Vaadin, a Web Components library): no form participation, broken autofill, broken accessibility, breaks SVG references, cannot extend built-in elements, handling focus, handling selection [2]
- Sarah Mei (Salesforce UX): Web Components break accessibility and assistive technology [3]
On top of that, you will always need a library/framework on top of them to orchestrate them, pass data around etc.
[1] https://dev.to/richharris/why-i-don-t-use-web-components-2cia https://dev.to/richharris/why-i-don-t-use-web-components-2ci...
[2] https://dev.to/webpadawan/beyond-the-polyfills-how-web-components-affect-us-today-3j0a https://dev.to/webpadawan/beyond-the-polyfills-how-web-compo... and https://dev.to/webpadawan/the-journey-of-web-components-wrong-ways-lacking-parts-and-promising-paths-1d5a https://dev.to/webpadawan/the-journey-of-web-components-wron...
[3] https://twitter.com/sarahmei/status/1198069119897047041 https://twitter.com/sarahmei/status/1198069119897047041