[w3c/webcomponents] Protocols/traits for custom elements (#811)

I have some high-level concerns around custom element form controls that I wasn't sure where to raise so I thought I'd bring them up here since they are mostly future-focused.

The current approach seems to be done in such a way that you can be both a form control and a link (if we added custom element links).

1. Is this desirable? I think in general the answer here is definitely as we need multiple protocols/traits for certain custom elements (e.g., focus, various ARIA bits, and form controls go together in some fashion).
2. What about clashes? I'm worried that we'll end up losing oversight of all the possible interactions.
3. Should we perhaps do a little bit of work on what the various extension points might be (focus trait, ariaDescribedBy trait, link trait, label trait, ...) and see if we can foresee issues somehow?

cc @tkent-google @domenic 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/811