Re: [w3c/webcomponents] Why can't the registry enumerate the custom elements? (#775)

> With that, you can make a query like "are any other date pickers available"? That type of usage—fetching components by the qualities that they possess, rather than their exact identity or location—would open up great potential for a component ecosystem.

I don't see a practical situation in which this would work. In order to use such a data picker component, the script has to understand how it communicates back the picked date & how to set the valid date range, etc... The most likely situation instead is that each component will end up embedding its own date picker.

Anyhow, I hate to keep repeating the same mantra, we really need more concrete use case than that kind of abstract notion of *it might allow use cases*. We need a solid, concrete, down-to-earth, I-can-write-it-tomorrow use case.

-- 
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/775#issuecomment-445343955