[whatwg] The src-N proposal

[Ilya Grigorik]

On Sat, Nov 9, 2013 at 2:49 AM, Markus Lanthaler
<markus.lanthaler at gmx.net>wrote:

> Well, an alternative would be to move the complexity to the server. I very
> much doubt that webmasters are going to create all those variations
> manually
> anyway. And if so, it's enough to store them according a naming convention
> the server understands. There are already two proposals how this could
> work:
>
>   http://tools.ietf.org/html/draft-grigorik-http-client-hints-00
>

^ I don't have the new draft up on the IETF tracker yet, so a few reference
links:

- Quick overview (plus interop with src-N/srcset):
https://github.com/igrigorik/http-client-hints#client-hints-internet-draft
- 01 draft:
https://github.com/igrigorik/http-client-hints/blob/master/draft-grigorik-http-client-hints-01.txt

FWIW, Client-Hints is part of the solution to the larger problem. CH
automates the resolution switching case (via CH-DPR), but we still need a
client-side markup solution to cover the other RICG use cases.. The CH-RW
hint in the new draft is implicitly relying on src-N - hence I would treat
that as an experimental idea. On the other hand, I think we have DPR
switching nailed - we have a prototype implementation under a flag in
Chrome, give it a try.