The end of responsive images - Piccalilli
Hallelujah! Support for sizes="auto" is finally landing in Firefox and Safari! Praise be!
Why we use progressive enhancement to build GOV.UK | Technology at GDS
This is a terrific read that gets to the heart of why progressive enhancement is such a solid methodology: progressive enhancement improves resilience.
Meeting our many users’ needs is number one on our list of design principles. We can’t know every different setup a person might use while building our systems, but we can build them in a way that gives all of our users the greatest chance of success. Progressive enhancement lets us do this.
The article is full of great insights from a very large-scale web project.
Related links
Optimizing PWAs For Different Display Modes — Smashing Magazine
There’s really good browser support for display-mode media queries and this article does a really good job of running through some of the use cases for your progressive web app.
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.
Progressive enhancement brings everyone in - The History of the Web
This is a great history of the idea of progressive enhancement:
It is an idea that has been lasting and enduring for two decades, and will continue.
Request for developer feedback: customizable select | Blog | Chrome for Developers
I’m very glad to see that work has moved away from a separate selectmenu element to instead enhancing the existing select element—I could never see an upgrade path for selectmenu, but now there are plenty of opportunities for progressive enhancement.
Related posts
Browser support
Here’s Clearleft’s approach to browser support. You can use it too (it’s CC-licensed).
Speculation rules
A performance boost in Chrome.
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.
Overloading buttons
Can you have too much semantics?