The end of responsive images - Piccalilli
Hallelujah! Support for sizes="auto" is finally landing in Firefox and Safari! Praise be!
Make Beautifully Resilient Apps With Progressive Enhancement
You had me at “beautifully resilient apps with progressive enhancement”.
This is a great clear walkthrough of enhancing a form submission. A lot of this seems like first principles to me, but if you’ve only ever built single page apps, then thinking about a server-submission process first might well be revelatory.
Related links
Don’t judge a book by its cover
Some neat CSS from Tess that’s a great example of progressive enhancement; these book covers look good in all browsers, but they look even better in some.
What You Need to Know about Modern CSS (2025 Edition) – Frontend Masters Blog
Here’s a comprehensive round-up of new CSS that you can use right now—you can expect to see some of this in action at Web Day Out!
Polishing your typography with line height units | WebKit
I should be using the lh and rlh units more enough—they’re supported across the board!
A pragmatic browser support strategy | Go Make Things
- Basic functionality should work on any device that can access the web.
- Extras and flourishes are treated as progressive enhancements for modern devices.
- The UI can look different and even clunky on older devices and browsers, as long as it doesn’t break rule #1.
Related posts
Simplify
Reminding myself just how much you can do with CSS these days.
Making the new Salter Cane website
A redesign with modern CSS.
Browser support
Here’s Clearleft’s approach to browser support. You can use it too (it’s CC-licensed).
Baseline progressive enhancement
If a browser feature can be used as a progressive enhancement, you don’t have to wait for all browsers to support it.
Progressive disclosure with HTML
The `details` element is like the TL;DR of markup.