W3C home > Mailing lists > Public > public-respimg@w3.org > August 2015

Steering gigantic ships

From: Eric Portis <lists@ericportis.com>
Date: Mon, 31 Aug 2015 11:56:04 -0600
To: public-respimg@w3.org
Message-ID: <71D9372C-775A-4594-9364-DB40A435E092@ericportis.com>
# Steering gigantic ships

## Edge progress

`picture` is officially [“In Development”][1] on Microsoft’s 
official status page. Even better: the latest Microsoft Edge build [now 
supports][2] `w` descriptors and `sizes`! Go Redmond, go.

[1]: 
https://dev.modern.ie/platform/status/pictureelement/?filter=f3f0000bf&search=picture
[2]: 
http://www.winbeta.org/news/heres-whats-new-in-microsoft-edge-on-windows-10-build-10532

## Bringing responsive images to WordPress core

The [official responsive images plugin for WordPress][3] currently 
sports “10,000+” active installs. Joe McGill recently penned [a post 
over on the WordPress Core blog][4] about the effort to land the 
plugin’s functionality in Core, so that all million-bajillion of 
WordPress’ users will get respimg functionality *automatically*.

Joe outlines the issues left to conquer (and there are more than a few 
of them — WordPress’ image-handling is old, stable, and resistant to 
change), and calls on all interested to contribute. [Contribute!][4]

[3]: https://wordpress.org/plugins/ricg-responsive-images/
[4]: 
https://make.wordpress.org/core/2015/08/25/responsive-image-support-update/

## 101 done

Jason Grigsby has completed his stupendous <cite>Responsive Images 
101</cite> series with a pair of posts: one on [image breakpoints][5], 
the other, a [conclusion][6].

Jason has thought about image breakpoints more than anyone — I’m 
pretty sure he coined the term? — and it shows. After outlining the 
problem and a bunch of different ways to think about tackling it, Jason 
ends with a section called “Humans shouldn’t be doing this” and a 
plea for developers and CMSs to shield content creators from having to 
do the confounding, tedious work of creating and managing multiple 
alternate image resources.

The conclusion to the series is excellent. Jason celebrates how far 
responsive images have come, touches on a bunch of possible “201” 
topics, and implores us all to “Please share what you learn!” Hear, 
hear!

[5]: 
http://blog.cloudfour.com/responsive-images-101-part-9-image-breakpoints/
[6]: http://blog.cloudfour.com/responsive-images-part-10-conclusion/

## Specs on the move

The WHATWG HTML spec moved from its lonely SVN server [over to 
GitHub][7] over the weekend. To date, Ian Hickson, WHATWG editor, has 
used a build script to pull `picture` from the [RICG’s repo][8] into 
the published WHATWG spec. As a result of the move, that workflow is 
being tossed. Henceforth, `picture` and friends [will][9] [live][10] in 
the WHATWG HTML repo, just like everything else.

Our venerable [`picture-element` repository][8] will live on for 
history, but all of the action is moving to the WHATWG HTML spec repo on 
GitHub. So if you’ve got a bug: [file it there][11].

[7]: https://github.com/whatwg/html
[8]: https://github.com/ResponsiveImagesCG/picture-element
[9]: https://github.com/whatwg/html/issues/52
[10]: 
https://github.com/whatwg/html/commit/d9cff6e9a6fb2928ef5d3f3d8df4e4dd18fb9b4c
[11]: https://github.com/whatwg/html/issues

See you in a couple of weeks!

—eric
Received on Monday, 31 August 2015 17:56:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:17 UTC