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

Use cases in the streets, rebases in the sheets

From: Eric Portis <lists@ericportis.com>
Date: Mon, 17 Aug 2015 14:05:05 -0600
To: public-respimg@w3.org
Message-ID: <D1771F62-48A8-4E17-889B-3F0E3B1FB85C@ericportis.com>
## Client Hints have landed in Blink

After [months][1] of [discussion][2] over on blink-dev, Client Hints 
finally got the magical “LGTM”s and support for the DPR, Width and 
Viewport-Width hints has [landed in Blink][3]. If all goes well, 
they’ll ship in Chrome 46.

Because he’s Yoav – the very same Yoav whose Blink username 
currently claims to be “Out of the Office until the 15th” – Yoav 
landed the commit [on shady wifi while on vacation][4]. As a great man 
once said,

> We shall land responsive image patches, whatever the cost may be. We 
> shall commit on the beaches, we shall express our intent to implement 
> in the [countryside][5], we shall read mailing lists in the fields and 
> compile use cases in the streets, we shall spec in the hills; we shall 
> never serve an [85.4MB website about sunglasses][6].

God Save Yoav. And if you’re interested in pushing the complexity of 
managing multiple resources out of your markup and onto a server, grab a 
fresh [Canary][7], brush up on the [spec][8] and give Client Hints a 
spin.

[1]:  
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/vvX1vCQihDE/wg6JQg9utaMJ
[2]: 
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ATbqmznya_k
[3]: https://codereview.chromium.org/1262253002/
[4]: https://twitter.com/yoavweiss/status/631505136075055105
[5]: https://twitter.com/yoavweiss/status/612883735864807424
[6]: http://hawksworx.com/blog/oakleys-monster-page-of-baubles/
[7]: https://www.google.com/chrome/browser/canary.html
[8]: http://igrigorik.github.io/http-client-hints/

## `picture` is coming to Edge

It’s [official][9]. No timeline yet (and their [status page][10] 
hasn’t even been updated), but: `picture` is coming to Edge. Which 
makes Webkit the last of the three major rendering engines not to have 
made a public commitment to implementing the full respimg spec.

There are, of course, [positive signs][11]. And Yoav’s [on][12] the 
[case][13].

[9]: 
https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6261271-picture-element?tracking_code=2bff73cbe7ab5df6de48a42bf23848f0
[10]: 
http://dev.modern.ie/platform/status/pictureelement/?filter=f3e0000bf&search=picture
[11]: https://twitter.com/grorgwork/status/616333173362786304
[12]: https://bugs.webkit.org/show_bug.cgi?id=134488
[13]: https://bugs.webkit.org/show_bug.cgi?id=picture

## Grab bag

- The Financial Times [implemented responsive images][14] on a new 
responsive design that they’re cooking up and saw a 66% decrease in 
total bytes transferred, and a 40% improvement on their Speed Index. Not 
too shabby.

- Chris Coyier published an excellent thirty-minute [screencast over on 
CSS Tricks][15] which walks through [a responsive images 
implementation][16] using Picturefill, `w` descriptors, and `sizes` with 
a design breakpoint. Uniquely, Chris delves into how to actually export 
the resources we need from layout comps in both Sketch and Photoshop. 
[Excellent!][17]

[14]: https://twitter.com/patrickhamann/status/626414825279778817
[15]: 
https://css-tricks.com/video-screencasts/141-getting-the-images-and-numbers-for-responsive-images/
[16]: http://codepen.io/chriscoyier/pen/QbVwYp
[17]: http://www.billandted.org/sounds/ea/eaexcellent.mp3

See you in a couple of weeks!

—eric
Received on Monday, 17 August 2015 20:05:45 UTC

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