Wilto/standings.md

## standings.md

      
    Raw
  

              standings.md
            
          
    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.