- From: Matthew Phillips <notifications@github.com>
- Date: Thu, 16 Mar 2023 07:07:27 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 16 March 2023 14:07:39 UTC
I find this thread fascinating because it gets into the heart of what the use-cases are for web components, and we can see that there are competing visions for what that is. I tended to side with @caridy and @domenic's idea, of web components being decoration on top of light DOM where the interesting stuff was. The current problem with this vision is that it only works if you are ok with the fallback. As an example: ```html <fancy-input> <input type="text"> </fancy-input> ``` This works as long as you are fine with regular `<input>`. But I think the thing we've seen over time is that people aren't ok with the default built-in elements. They find them lacking. And that's why they desire to build better ones.' The fix for this problem would be, the built-in elements need to get better. Probably much better. If that happens then the fallback is not so bad, and so using web components for extra nice-to-have decoration starts making more sense. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/986#issuecomment-1472048690 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/986/1472048690@github.com>
Received on Thursday, 16 March 2023 14:07:39 UTC