Skip to content

@Wilto /standings.md
Last active

Embed URL

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Wondering what the current standings are for the Responsive Images Community Group’s efforts? Look no further.

Mozilla

Bug 870021 Summary: Implement srcset attribute on img CLOSED: WONTFIX:
https://bugzilla.mozilla.org/show_bug.cgi?id=870021

Bug 870022 Implement picture element:
https://bugzilla.mozilla.org/show_bug.cgi?id=870022

Implement src-n attribute on img element:
https://bugzilla.mozilla.org/show_bug.cgi?id=936481

Mozilla does not support srcset, has requested that it be dropped from the WHATWG spec, and is willing to explore the picture or src-n markup patterns.

Google

src-n was proposed by a Google rep:
http://tabatkins.github.io/specs/respimg/Overview.html

Divided on src-n in the discussion thread:
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/tV3T1wHuXqE/SvWKxIyG6IIJ

Unlikely to move on anything unless WebKit does it first:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-November/041397.html

Client Hints refactor includes src-n:
https://github.com/igrigorik/http-client-hints/#interaction-with-src-n

Apple

Officially silent. Adam Barth is doing the talking on behalf of WebKit on the WHATWG list—and is not a fan of the src-n pattern—but he officially represents Blink, not WebKit:
See http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-November/041397.html, above.

Microsoft

Silent.

WHATWG List

“Has anyone thought about using CSS?”

Maciej Stachowiak (WebKit) already shut this idea down for the obvious reasons, but hasn’t officially said anything about src-n (see: “Apple,” above).

HTML WG

Silent.

@marcoscaceres

HTMLWG is silent because they are all in China for TPAC, I think. Also, the discussion is not really happening there :)

@Wilto
Owner

No blame intended! Just figure this is gonna be a template for rapid-fire digest updates, going forward. Maybe a weekly thing?

@yoshokatana

This format is fantastic. I knew about Mozilla's srcset / src-n kerfuffle (and had to refrain from getting into a flamewar), but I didn't really know the positions of the other players. Isn't srcset at least mostly implemented in chrome-stable?

@chadsten

It's better than keeping with the discussions on #responsive, and all of the random articles. Thanks for the gist.

@roblarsen

Well, there's the one quote about src-n from Timothy Hatcher (Apple) " It is a grotesque perversion of the HTML language. Everyone seems to be taking that as evidence of the party line from Apple.

@dmethvin

Paraphrasing Churchill, src-n is the worst form of responsive images, except for all those other methods that have been tried.

@iandevlin

Good to see this altogether in one list, nice work Mat.

@scshepard

Is Apple even in the browser race anymore? Seriously?

@AurelioDeRosa

The srcset proposal has landed into the W3C specifications (http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/) . So, the HTML WG is not silent anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.