There are 16 contents with this tag:
Progressive Enhancement: Where Do I Begin?
Aaron shares the slides of his latest talk about progressive enhancement, a topic he's been talking about for a while, with his book "Adaptive Web Design: Crafting Rich Experiences with Progressive Enhancement" really high in my list of best books about developing for the Web the right way.
Is Progressive Enhancement Dead Yet?
Progressive enhancement is Scary Mary™ to some but there is no need to cry or pass out. Let me use a shark in a fez, Tony Hawk, and a couple of zombie lads to explain. Shout out to my pal Andy whose skateboard/scooter analogy I borrowed.
“Evergreen” Does Not Mean Immediately Available
With the actual, final, no-seriously-we-mean-it-this-time death of Internet Explorer, evergreen browsers are now the main consideration for desktop and laptop browsers. This is great! It means we can spend a lot less time fretting about who can use what.
Internet Explorer’s Decline in Usage in 2021
We all want IE11 to be ancient history. Unfortunately, some people still use it. A lot more than I thought, in some countries:
Seing @basecamp's Hotwire reminds me a lot of Hijax. @adactio made a nice presentation back in 2006!
Please disable JavaScript to view this site
Most of the web sites I visit on an average day require JavaScript to allow me to navigate the site fully. At least once a week there will be a web site that fails to fully load JavaScript for me and I'll (rage) quit the site and usually committing it to a bank of "web sites I can't be arsed to ever visit again because they messed up".
as the device landscape continues to converge, the categorizations will continue to blur. And as you introduce more interactivity and complex features to your site, the singular approach starts to break down.
Great article where Kitty shows how React helps providing N26 clients the features they're looking for even if they unfortunately have JavaScript issues.
The layered approach of progressive enhancement echoes the separation of concerns in the front-end stack: HTML, CSS, and JavaScript—each layer expressing more power. But while these concepts are related, they’re not interchangable. Separating out the layers of your tech stack isn’t necessarily progressive enhancement. If you have some HTML that relies on JavaScript to be useful, then there’s no benefit in separating that HTML into a separate payload. The HTML that you initially send down the wire needs to be functional (at least at a basic level) before the JavaScript arrives.
In defence of graceful degradation and where progressive enhancement comes in
Interesting explanation about graceful degradation not being the opposite of progressive enhancement.
If you don't understand why CSS is one of the great strengths of the Web, even if you've been using it for a while, you really have to spend these 15 minutes to watch Miriam Suzanne explain how it came to be, and why it is what it is.
The power of progressive enhancement
Here's another nice take about progressive enhancement, where Andy Bell explains how he developed My Browser, a nice tool for support.
Publishing a draft originally written in 2015, Remy shows Progressive Enhancement is still a strong topic all developers should understand and work on:
On the importance of testing with content blockers
To build good websites, I think we should prioritise working websites above gathering potentially useful data (if doing that at all). As developers, we should keep in mind trackers could get blocked and, consequently, never rely on their availability.
If you’re going to build an image loader that hides the whole page until all images are ready, you must also ask yourself what if the images don’t arrive?
Awesome post about progressive enhancement:
See all tags.
Aaron Gustafson
Heydon Pickering
Eric Bailey
Paul Calvano
Remy Sharp
Matt Anderson
Kitty Giraudel
Jeremy Keith
Adam Silver
Miriam Suzanne
Andy Bell
Hidde de Vries
Harry Roberts
Chris Taylor