Thread by @dmitriid

Web Components are *not* using the platform. It's easy to show. They keep changing the rules of what "the platform" means, but they are still not using it, unlike literally everyone else.

Ironic because they are in a very literal sense a part of the platform themselves

1/7

Web Components: The only tech that struggled to create form components that would be seen by the browser and sent as a part of the payload.

Had they used the platform, this would be a non-issue. So they changed the rules:

2/7web.dev/articles/more-…

This didn't help much. In 2023 there's still an open issue that a web component cannot be a submit button:

Had they used the platform, like everyone else, this would be a non-issue.

They are changing the rules on this, again:

3/7github.com/WICG/webcompon…
developer.mozilla.org/en-US/docs/Web…

Web Components are HTMLElements. So they cannot subclass, or encapsulate SVG, or be used inside SVGs

Had they used the platform correctly, this would be a non-issue, as it is a non-issue, you guessed it, for everyone else.

They are not changing the rules on this (yet?)

4/7

In 2022 Web Components Community Group released their first status report:

It shows that Web Component need to change the rules 20 more times. Literally none of them are issues for projects that use the platform. Including the critical ones like ARIA

5/7w3c.github.io/webcomponents-…

And as some proponents of "use the platform" decry the increased usage of JS on the web, Web Components are continuously changing the rules by requiring more and more JS for them to be able to do work that literally everyone else can already do.

6/7

Next time a Web Component proponent asks you to "use the platform", tell them: "Already am. Are you?"

7/7