You know, we use ad-blockers as well. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf San Francisco, dedicated to smart front-end techniques and design patterns.
Mat “Wilto” Marquis is a designer-slash-developer working at Filament Group, in Boston. Mat is a member of the jQuery Mobile team, an active member of the open source community, and a contributor to A List Apart where he also acts as technical editor and curator. Mat's passion for responsive Web design has led him to chair the Responsive Images Community Group, where he’s helping the web design community deal with the complex topic of responsive images and working towards a standardized solution with the W3C.
WebKit has made some serious news by finally implementing the srcset attribute. As Chair of the W3C’s Responsive Images Community Group, I’ve been alternately hoping for and dreading this moment for some time now. It turns out to be good news for all involved parties—the users browsing the Web, most of all.
As with all matters pertaining to “responsive images”: it’s complicated, and it can be hard keeping up with the signal in all the noise. Here’s what you need to know. As originally proposed, the srcset attribute allowed developers to specify a list of sources for an image attribute, to be delivered based on the pixel density of the user’s display: