- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Sun, 20 Oct 2013 14:57:27 -0700
- To: Jason Grigsby <jason@cloudfour.com>
- Cc: Marcos Caceres <w3c@marcosc.com>, John Mellor <johnme@chromium.org>, "public-respimg@w3.org" <public-respimg@w3.org>
On Sun, Oct 20, 2013 at 12:20 PM, Jason Grigsby <jason@cloudfour.com> wrote: > On Fri, Oct 18, 2013 at 10:58 AM, Tab Atkins Jr. <jackalmage@gmail.com> > wrote: > >> Please review >> <http://tabatkins.github.io/specs/respimg/Overview.html#viewport> >> (or >> <http://tabatkins.github.io/specs/respimg/Overview.html#variable-size>, >> once github's cache clears) and let me know if it's clearer! > > > This is clearer. Thanks for working on it. The description currently says: > > "The breakpoints must be in ascending order, as the image size is chosen by > finding which two breakpoints the viewport’s size sits between, and > selecting the image size between those two." > > Which makes sense for every viewport size except one that exactly matches a > breakpoint. What happens then? This is defined in the algorithm - it takes the higher image size, as if you were using min-width MQs. RICG people told me this was better than the alternate behavior. ~TJ
Received on Sunday, 20 October 2013 21:58:14 UTC