4 ms·

Very much this. I work on a "web app" with all custom components, even the most basic input is a custom component... everything about it sucks. Keyboard navigat

Very much this. I work on a "web app" with all custom components, even the most basic input is a custom component... everything about it sucks. Keyboard navigation sucks and is redone poorly, dropdowns are godawful, styling them is no joy. I don't know what our way out of this is. Everyone imagines their own UX and wants this or that thing to behave differently from everything else out there on the web. We'd have more usable webpages (and web apps) if we didn't spend most of our time reinventing the button... over and over and over

Andrex 8y ago
If Web Components don't save us, nothing will. Thankfully I'm pretty bullish on them (especially customized built-in elements.) The future is bright.
- arenaninja 8y ago
  I've heard about this but I'm not so sure. From my limited experience, the customization is as bad or worse than say React components. And then there's the whole shady/shadow DOM. And from my experience the way that components are currently used, "slots" can get you in a lot of trouble. This is without mentioning the severe fragmentation in that space (polymer vs skatejs vs stencil vs ....)
  - Andrex 8y ago
    Shadow DOM v0 was kind of a mess (the fragmentation you mention), but v1 kinda washed all that bad taste away and is a pretty sane API. I don't see libraries building on a feature as "fragmentation," however. Slots are a powerful feature that has to be used carefully. But it's a great API foundation for a lib (which is a tendency for web platform drafts, ex. WebGL and Web Audio.) Customization is just CSS, I'm not sure about the comparison to React. For Shadow DOM styling, we're almost at the point where the last big problem (selective and scalable piercing styles) are getting solved. In any case, the world is better with Web Components than without. Combine them with ES Modules and you have an great ideal for the web platform to strive towards.
    - arenaninja 8y ago
      I do hope to see them picked up. I'd like to see the next Bootstrap/Foundation/Material UI framework be web components, that'd be a sight

Andrex 8y ago

If Web Components don't save us, nothing will. Thankfully I'm pretty bullish on them (especially customized built-in elements.) The future is bright.

arenaninja 8y ago
I've heard about this but I'm not so sure. From my limited experience, the customization is as bad or worse than say React components. And then there's the whole shady/shadow DOM. And from my experience the way that components are currently used, "slots" can get you in a lot of trouble. This is without mentioning the severe fragmentation in that space (polymer vs skatejs vs stencil vs ....)
- Andrex 8y ago
  Shadow DOM v0 was kind of a mess (the fragmentation you mention), but v1 kinda washed all that bad taste away and is a pretty sane API. I don't see libraries building on a feature as "fragmentation," however. Slots are a powerful feature that has to be used carefully. But it's a great API foundation for a lib (which is a tendency for web platform drafts, ex. WebGL and Web Audio.) Customization is just CSS, I'm not sure about the comparison to React. For Shadow DOM styling, we're almost at the point where the last big problem (selective and scalable piercing styles) are getting solved. In any case, the world is better with Web Components than without. Combine them with ES Modules and you have an great ideal for the web platform to strive towards.
  - arenaninja 8y ago
    I do hope to see them picked up. I'd like to see the next Bootstrap/Foundation/Material UI framework be web components, that'd be a sight