The time is right for a DOM templating API

It’s worth noting this was written by maybe the person with the most experience in the space i can think of—-the primary author of Lit / Polymer working at web components on Google and contributing on many core DOM specs that have become part of the web platform.

> It’s worth noting this was written by

by one of the people wrecklessly barging forward with half-baked specs that introduced significantly more problems than they solved, pushed a "solution" that requires 20+ new web specs to barely do all the things user-space is already doing while completely ignoring and gaslighting anyone who wasn't 100% on board with what they were doing.

Safari argued that there should be a declarative ways for this 15 years ago

What were these 20 new specs?

After multiple specs had already been pushed through, they finally decided to write down a list of what is still needed.

22 items: https://w3c.github.io/webcomponents-cg/2022.html

In those things like ARIA are not a single spec. It's now close to five different proposals and a huge ARIA Object Model proposal.

Similar thing with Form Associated Controls: it's not one spec. It's a bunch of specs fixing idiotic issues like this: https://github.com/WICG/webcomponents/issues/814

Note: easily half of these only exist because of web components and for web components. Literally nothing else has these issues.

Right but what were these required specs for the existing implementation?