[troupo]

> Do you have any concrete examples there? What "mechanics" are you referring to

Try the 2022 Web Components Group Report. Including things like "most these issues come from Shadow DOM".

> Given that very complex apps like Photoshop, Reddit, The Internet Archive, YouTube, The Microsoft App Store, Home Assistant, etc., are built with web components, that would make the claim that they're unusable seem silly.

Trillion dollar corporations also build sites in Angular, or React, or Blazor, or...

[spankalee]

So you're saying that the web components community ignores the issues with web components by... writing a report on the issues with web components?

I still don't know what "mechanics and assumptions" are baked according to the OP.

[troupo]

So you're deflecting from the original point raised.

Anyway, yes. Web Component "community" was fully and willfully ignoring most issues that people (especially framework authors) were talking about for years.

At one point they managed to produce a single report (very suspiciously close to what people like Rich Harris had been talking about since at least three years prior for which he got nothing but vile and bile from main people in the "community"), and then it went nowhere.

> I still don't know what "mechanics and assumptions" are baked according to the OP.

Again: you do, people who wrote the report do, but you all keep pretending that all is sunshine and unicorns in the web component land.

While the report very explicitly calls out a very major behaviour baked in, for example. And calls out a bunch of other issues with behaviours and mechanics. While web components need 20+ specs to barely fix just some of the assumptions and baked in mechanics (that literally nothing else needs, and most of which exist only due to web components themselves).

Anyway, I know you will keep pretending and deflecting, so I stop my participation in this thread.

Adieu.