Great article at a list apart discusing the state of the industry regarding responsive images. This picks apart the set attribute of the img element from a surprisingly objective view coming from someone so close to the picture element. Insightful discussion about the principle behind the proposals than the actual solution too. If the working group wants the community to be involved and then ignores it in favor of "their own" biased unproven/untested ideas.
A List Apart: Articles: Responsive Images and Web Standards at the Turning Point
The goal of a “responsive images” solution is to deliver images optimized for the end user's context, rather than serving the largest potentially necessary image to everyone. Unfortunately, this h…
Bruce details the reasons and story behind the srcset attribute which is now introduced as an alternative to the picture element. Some aspects of the attribute are nice (like the fact that it's an attribute and not a new element, so it's creating up new elements with for problems. It's adapting currently used elements to be more future-friendly), but some aspects are weird – like the totally foreign syntax (where did that come from?). There is also some worry that the elements that are proposed and introduced by the community get nowhere, but then a when someone at apple makes a proposal it gets new immediate support from the group. Anyways, either way I think one of these solutions (or a variant) should help alleviate much of the pain behind responsive images. At least the discussion is happening, no?
HTML5 adaptive images: end of round one | HTML5 Doctor
Those web authors in the W3C Resposive Images Community Group soldiered on in frustration that they were they being ignored because the problem itself wasn't seen as a problem. Then this week, Edw…
Here's another recap on the state of responsive images. This one from the Filament Group, who was involved in the Boston Globe redesign. It discusses their solutions and the problems with them and then the newly suggested picture html element and a call for the need of bandwidth detecting media queries. I'm still concerned about bandwidth detection. I think somehow there should be a setting that lets users decide if they want high res images (when supported) or the faster low res images. If I'm just browsing on a laptop tethered to a phone with 4g and paying for every kilobyte, I may not want to download a large image just because I can. I agree we need better ways to server appropriately sized images, but I don't want to force anything on a user. Although a popup asking them if they want every large image is not practical either… I'm glad this discussion is continuing though!
The state of responsive images | Feature | .net magazine
Designer/developer Mat “Wilto” Marquis takes a look at the img tag, explains why a largest-size-fits-all approach to images is untenable and discusses different solutions in this ongoing saga
I'm not going to get into the discussion on whether or not semantics are important, but want to share this flowchart for those who are interested in making a sensible web. It will help determine what HTML5 element is best for elements. Thanks fo the HTML5 doc!
Let’s Talk about Semantics | HTML5 Doctor
It's time we had “the talk”. I could get you a book or recommend some sites from Dr Mike's special bookmarks folder, but the best way to make sure you get the right idea is to do it myself. I&…
Thanks to Chris for this high level evaluation of the state of responsive images. THis post lays out descriptions pros and cons of each of the 3 foreseeable options: a new image format, a new syntax/html element or use existing technology.
On Responsive Images | CSS-Tricks
There are three ways we can go about dealing with responsive s : 1) a new format 2) a new syntax 3) rely on existing hacks.