- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 9 Oct 2013 10:30:59 -0700
- To: Rick Byers <rbyers@chromium.org>
- Cc: Simon Sapin <simon.sapin@exyr.org>, Alex Bell <alex@bellandwhistle.net>, "www-style@w3.org" <www-style@w3.org>, "eae@chromium.org" <eae@chromium.org>
On Wed, Oct 9, 2013 at 8:08 AM, Rick Byers <rbyers@chromium.org> wrote: > Note that there's been several recent discussions on blink-dev about this, > eg: > https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/RyUSi3zdumQ. > https://code.google.com/p/chromium/issues/detail?id=177836 > > The consensus was to match FF behavior and update devicePixelRatio and > associated media queries to reflect browser zoom - that this was both > consistent with the standard for the 'resolution' media query, and > sufficient for application needs (with Google Docs as an example of a very > demanding applications here). There was even rough agreement that this was > better than exposing two separate concepts (pixel ratio and browser zoom > level) to the application - that doing so would just lead to bugs and > applications should be treating both in the same way. > > I don't personally have more detailed context than that, but this sounds > like a much better path than introducing another new API. Yeah, this is much better. Obviously, the existing 'resolution' media query would reflect that as well. (Well, it would reflect its inverse.) ~TJ
Received on Wednesday, 9 October 2013 17:31:46 UTC