Twenty-four Percent

# Twenty-four percent

The RICG aims to responsify the web’s images; I’ve always thought of 
that as a three-part problem. We needed to get respimg features into 
specs, browsers, and, most important of all, websites. That last one was 
always going to be a long slog, so I’m overjoyed to report some huge, 
wonderful news: [the RICG’s official WordPress plugin has been merged 
into WordPress Core][1].

[24%+ of the web][2], here we come!

To Joe McGill and the whole team behind the WordPress plugin: huge 
congrats and even bigger thanks.

[1]: https://core.trac.wordpress.org/ticket/33641#comment:9
[2]: https://wordpress.org/about/features/

## This Picturefill goes to 3.0.1

A couple of weeks ago, I reported that Picturefill 3.0 — a 
near-complete re-write bringing spec-accurate parsing, robust tests, and 
fixes for niggling browser bugs in the extant implementations — was 
imminent. Welp, the team did me one better and released 3.0.1 last week. 
[Go update!][3]

So... what now? Picturefill was always meant to be a bridge — 
shepherding us all from a world without native implementations into a 
world with universal support. Now that almost every current shipping 
browser supports almost every respimg feature, Alexander Farkas (who was 
a driving force behind the PF3 effort) [has some ideas][4] on how 
Picturefill can start reducing its footprint. I find the fact that 
Picturefill was *designed* to slowly erase itself — to do less and 
less over time instead of piling on features ad infinitum — 
fascinating; PictureFill as a study in how to practically accelerate the 
progress of the web has always been fascinating to me too. I’m not 
close enough to the project to know if the time is right for 
Alexander’s ideas, but they’re definitely worth a [read-through][4].

[3]: https://github.com/scottjehl/picturefill/releases/tag/3.0.1
[4]: https://gist.github.com/aFarkas/dcc87311232987591a16

## Keep ’em coming

It’s been a good fortnight for respimg articles and tutorials.

- Chen Hui Jing published [an excellent intro][5] over at A List Apart.
- Greg Whitworth, the man behind Edge’s respimg implementation, posted 
[another great intro][6] over on the Microsoft Edge Dev Blog.
- Video of a typo-prone, nervous nelly [presenting at SmashingConf][7] 
has surfaced.
- You can’t read it online yet, but I have a respimg article in the 
[latest Net Magazine][8], too.

[5]: http://alistapart.com/article/using-responsive-images-now
[6]: 
https://blogs.windows.com/msedgedev/2015/10/07/using-extended-srcset-and-the-picture-element-to-tailor-your-image-to-every-device-and-layout/
[7]: https://vimeo.com/140641364
[8]: http://www.creativebloq.com/net-magazine

## Grab bag

- Yoav has been cleaning up a couple of nasty viewport size bugs in the 
Chrome pre-parser. If you’ve noticed double-downloads on either 
[viewports that have a `width=device-width`][9] or [mobile viewports 
that rely on the default viewport][10], fixes are on the way! And big 
thanks to all of the good people that have been [reporting][11] 
[these][12] [bugs][13].
- Tell [14][14] little bit about your image breakpoints and it’ll 
chart out the range of sizes that image will occupy on the layout and 
spit out a markup snippet, too.
- If all goes according to plan, lazyload scripts of the future will 
leverage [Intersecton Observers][15].
- Finally, Brad Frost is [starting to write a little about Container 
Queries][16] in his in-progress book on Atomic Design.

[9]: https://code.google.com/p/chromium/issues/detail?id=526630
[10]: https://code.google.com/p/chromium/issues/detail?id=531820
[11]: 
http://stackoverflow.com/questions/32941158/why-is-srcset-causing-images-to-download-multiple-times
[12]: 
http://stackoverflow.com/questions/32841724/picture-tag-uses-wrong-source-on-chrome-on-android
[13]: http://terraling.github.io/srcset-sizes/
[14]: http://responsivizr.com
[15]: 
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/eLxh8xUp3j4/m7RH4_nLBgAJ
[16]: 
http://atomicdesign.bradfrost.com/chapter-3/#viewport-tools-for-flexible-patterns

See you in a couple of weeks!

—eric