‘Accessibility is not a “React Problem” - Netlify’
Loads of useful pointers.
“ICONSVG - Quick customizable SVG icons for your project”
These look really nice to use.
“I Ditched Chrome for Safari and You Can Too”
In my day-to-day I’ve also switched to either Firefox or Safari. Firefox is great for dev; Safari is great for browsing. I use Chrome mostly as a sandbox to isolate work Slack.
‘“If you care about your thoughts, keep them.” – Shawn Blanc’
Somewhere, in an alternate universe, Apple’s rebirth came from an acquisition of BeOS and Steve Jobs is most famous for being the founder that flamed out in the 80s
“How to Respond to Skepticism of Testing Small Groups of Users”
“GitHub - lagmoellertim/cryption: In-Browser AES File Encryption with Data Integrity Check”
“Announcing npm Enterprise and why it matters to the community! - 📣 announcements - npm forum”
“Verdana, Helvetica, and Times New Roman all do well in tests, and usually do better than dyslexia-specific fonts (e.g. Open Dyslexic) because they are familiar”
“When it’s OK if a browser doesn’t support a feature - Go Make Things”
Am wondering what those with more expertise in search think about this:
“Postgres full-text search is Good Enough!”
“You probably don’t need a single-page application”
“Even if your app needs some real-time capabilities or rich interactions, you don’t need to use the SPA paradigm for your whole app.”
“Michael Tsai - Blog - T2 Macs Have a Serious Audio Glitching Bug”
Discussion.
“Apple’s latest Macs have a serious audio glitching bug - CDM Create Digital Music”
“Apple has shipped their entire computer line with buggy firmware that renders those machines unusable for the majority of people working with sound”
“Apple’s latest Macs have a serious audio glitching bug - CDM Create Digital Music”
This is pretty bad.
“JavaScript-free accordions - Go Make Things”
I love the details/summary elements. They are especially useful for quickly prototyping all sorts of widgets in HTML and CSS.
“Enhanced Tracking Protection Testing: Protecting users’ privacy by default - Future Releases”
Is there a specific reason why web devs these days generally don’t use the EventListener.handleEvent pattern to address issues with ‘this’ in JS events? IME it’s generally a no-cost, win-win-win solution.
“Trolling isn’t outlier behavior, and we can stop it - Community Manager Musings”