Notices by Mayank (mayank@front-end.social), page 3

📝 new blog post: "Your CSS reset should be layered". https://www.mayank.co/blog/css-reset-layer

i've been wanting to publish this one ever since i built my own CSS reset. i waited until layers were "baseline widely available"

@sarajw lessgooo CSS

i'll be curious to hear how it goes with React Aria Components. they do some weird things, is my understanding

@sarajw oh APG is a whole another topic (and yes problematic). but i was getting at something different here:
- React Aria tends to laser focus on SR experience, to the point that they add lots of code to work around SR quirks (not always a good thing).
- they abstract away the DOM too much (e.g. made-up "press" events) which could be a hindrance when you need control. they also overload the `slot` attribute, which can cause problems if you use shadow DOM.
- their components are not polymorphic.

@matovius @sarajw there's good parts and bad parts. APG only shows you how to use ARIA (which may not even be supported), it's not a production-tested pattern library to use as a blueprint. that's why there's a prominent warning on every page

@binarydigit i love that waterfox is independent and that it's one of the only browsers built upon gecko. i daily'd waterfox for a while before i moved onto zen browser, which i like more.

tbh none of the browsers are as good as they should be (or maybe i'm just too picky).

@binarydigit right? it feels half-baked and misleading. work cookies mixing with personal cookies and whatnot

@binarydigit interested in how you'll like it. my experience left a lot to be desired: https://front-end.social/@mayank/112793398800816572

i do like their AI statement https://vivaldi.com/blog/technology/vivaldi-wont-allow-a-machine-to-lie-to-you/

@aral it looks still open source (at least partially)? https://github.com/tldraw/tldraw/tree/main/apps/dotcom/client

@aral @zens this sort of thing should probably be a fragment link. currently a screen-reader user does not get any feedback after clicking the link; it's as if the link were broken. in comparison, clicking a fragment link would move focus to the target element, which gets announced by screen-readers.

i've made a thing: https://xkcd.fyi/

it's an alternative frontend to https://xkcd.com/ with some important differences:
- title text shown in a more accessible way (instead of abusing alt text)
- transcript included for every comic (with newer ones sourced from explainxkcd)
- link to https://explainxkcd.com/ (for when you don't get the joke)
- dark mode!

@cory @binarydigit i switched over to vivaldi (https://front-end.social/@mayank/112779689193704778) and now i'm probably switching again (https://front-end.social/@mayank/112793398800816572)

modern browsers are all annoying in different ways

@aral it's wild that your *very* reasonable take was considered so controversial that it offended people to the point they feel the need to publicly announce they're unfollowing you. if anything, this only helps show the ableism that's so deeply ingrained in the average fossbro