Skip to content

Latest commit

 

History

History
63 lines (40 loc) · 4.22 KB

RICG-newsletter-2016-01-04.md

File metadata and controls

63 lines (40 loc) · 4.22 KB

Happy New Year!

Teaser: WordPress, WebKit, WooHoo!

As the newsletter wakes from its long winter’s nap, let me wish everybody a very happy new year! What happened while I was away? Lots!

WordPress 4.4 happened!

WordPress 4.4 was released, bringing responsive images to the biggest CMS on the planet.

Predictably, this resulted in the biggest uptake in responsive image usage, ever. A month ago, one in every 2,500 pages sampled by Chrome used w descriptors. Now that number is 1 in 500 and quickly climbing.

So, once again, let me thank the team behind the effort. To Joe McGill, Tim Evko, Jasper DeGroot, and everyone else who lent time and energy to respimg-in-WordPress: thanks for making the web a faster, better, and more responsive place.

(And for an excellent technical overview of how 4.4 actually goes about it’s responsifying, read this post by Fränk Klein over on the WP Best Practices blog)

So did picture in WebKit (sorta)!

The picture bug in WebKit is now RESOLVED FIXED, and WebKit are announcing that picture “has landed”.

This is true! But, if you’ll allow me to over-extend the metaphor, the implementation is still taxiing towards the gate.

picture in WebKit (which you can test by downloading WebKit Nightly) currently has some issues with double-downloads, and doesn’t yet respond to viewport changes. Luckily the implementation will have plenty of time to mature, as it (probably) won’t be ported over to shipping Safaris until their next major version bumps in the fall.

But! In the Fall! Mobile and desktop Safari will (probably) ship with complete responsive images implementations! And the last big gap in respimg support will be filled. Huzzah.

2016: Year of the Container Query?

The end of 2015 brought a lot of new thinking and tinkering on the evergreen topic of Element/Container Queries. Tommy Hodgins and Maxime Euzière have registered elementqueries.com; in addition to housing their EQCSS Javascript library there, they’ve used the domain to publish loads of demos and collected a comprehensive list of element/container query resources. Check it out!

And over on 24 Ways, Jonathan Snook gives a very nice executive summary of the what and why of container queries, surveys the current landscape of prollyfills and experimental implementations, and shows how Shopify is actually prollyfilling Container Queries in production (!).

Grab bag

See you in a few weeks! —eric