4 ms·

This is how you do web components. Tightly scoped, no framework dependencies, no stylesheets, made with aria accessibility in mind. Good stuff.

• deleted 6y ago
  [deleted]
• 40four 6y ago
  Yes these look excellent, will have to try them out soon! You’re right, you can tell accessibility and compatibility were considered here. I haven’t looked at them all yet, but I noticed the autocomplete element uses XmlHttpRequest versus Fetch.
  • no_wizard 6y ago
    you get better portability that way. They still serve corporate markets where IE 11 access is a requirement.
    • 40four 6y ago
      Yeah for sure. I appreciate that they chose that route for compatibility. I know I don’t in my hobby projects :)
• inbx0 6y ago
  Some of them have stylesheets, for example https://github.com/github/image-crop-element/blob/main/src/index.css https://github.com/github/image-crop-element/blob/main/src/i...
• rektide 6y ago
  Personally, I'd really like to see the unmolested, with-dependencies versions[1]. This version is VERY easy to ship and adopt. But in my mind, these components hide how the sausage is made! Many were built with a library (Catalyst[2]), but the tools were obfuscated out in these end products. There's a huge amount to be said for these web components. We need more models like this. But I also think there's an opportunity lost here, to teach, to inform, to help others learn how to build components, using the tech Github actually used to develop them. [1] https://news.ycombinator.com/item?id=26439167 https://news.ycombinator.com/item?id=26439167 [2] https://github.com/github/catalyst https://github.com/github/catalyst