frend.co

A couple of points we can address here: Agree on the NodeList.prototype reassign - not a well informed decision (see source comments around its inclusion). We think it's worth correcting: https://github.com/frend/frend.co/issues/64 Fully aware of the less-than-ideal DOM traversal in places - this is ripe for improvement: https://github.com/frend/frend.co/blob/gh-pages/_components/... Let's shift the focus from code style to getting these components tested and improved for all users.

Thanks Stevoski. An issue has been filed for this: https://github.com/frend/frend.co/issues/62

The code style here looks really weird - for example, the 4 space hard tab is a rarity with JS: https://github.com/frend/frend.co/blob/gh-pages/_components/... . Lot of rough edges there, such as not making use of Array.from(nodeList).forEach instead of brute forcing on the prototype. There's also some nasty DOM traversal as well in some of these components. It should also be noted that these aren't web components in the Web Components sense - the title is very misleading. These are just vanilla components.

We've been building a collection of front-end components with a focus on accessibility and modern standards, and are keen to collaborate with more developers. The purpose of Frend is to not only offer these components for use in projects, but to also discuss the features that make them accessible. We'd like to continually improve upon them, to ensure they're predictable and supporting assistive technologies in all the ways they should. Read more about the project on the website: http://frend.co/about/ Contributions are welcome via the GitHub repo: https://github.com/frend/frend.co