Nathan Knowler
@knowler
Building web stuff and design systems. Focused on accessibility, progressive enhancement, and web components. At the intersection of CSS and the Shadow DOM. he/him Métis/settler Treaty 1/wpg
I can upgrade this markup to be a functional, semantically accessible, and customizable accordion without adding an attribute or element to its light DOM structure and it will work in any framework. Load the custom elements early and you skip any layout shift. Why aren’t more people doing this?
me whenever someone brings up `content-visibility` or `hidden=until-found`
spotted today ```html <label id=label for=control>Control</label> <input id=control aria-labelledby=label> ```
Anchor positioning works really well for the "label in the place of a placeholder" pattern, except instead of (ab)using a placeholder, you can use a real label.
I like this design pattern where if the first icon isn't clear enough, you just add another one /s
After two years of playing Celeste passing the controller back and forth with my now almost six year old, we finally beat it this afternoon!
I love this little Great Divorce reference on the jacket of the Callous Daoboys' "I Don't Want to See You in Heaven."
I use it too, but I wonder if that’s just because it’s there—it taps into my impulsive need to dismiss stuff. I find it to be so infuriating to use on the web because the hit target is the size of the icon inside and sometimes it seems like timeline items’ hit area overlaps with it.
This continues to be the most useless piece of UI on this site. The hit target is like half the size of the circle too.
They differ slightly. Find in page does nothing. Text fragments will scroll the page to the location, highlight the matching text briefly before disappearing (i.e. content stays hidden while in view). User needs to scroll content out of view and back in for it to show up properly.
