custom-elements-everywhere icon indicating copy to clipboard operation
custom-elements-everywhere copied to clipboard

caniuse style information?

Open theScottyJam opened this issue 3 months ago • 0 comments

This webpage seems to currently be built for framework authors and consumers, showing them a checklist of things they still need to do to be properly compatible with web components.

What would be nice is if the webpage had an alternative (or replacement?) view for those who wish to use web components, that could answer questions such as:

  • How should I design the API, such that it's maximally compatible with the most frameworks?
  • If I choose to not do support X, how harmful would that be? Which frameworks would have a hard time using my components?

For example, I'd be interested in knowing if I really have to support both attributes and properties when I build custom elements. How harmful would it be if I made my life simpler and exclusively supported properties only, ignoring attributes. If there were "caniuse"-style table for both attributes and properties that listed different frameworks and how they supported them, that would greatly help me answer these kinds of questions.

I'd be willing to help out if there is desire to do this, but I wanted to first throw the idea out there.

theScottyJam avatar Nov 24 '24 09:11 theScottyJam