W3C home > Mailing lists > Public > www-style@w3.org > March 2013

Re: [css3-values] recommendation for pixel units

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 21 Mar 2013 18:40:48 +1300
Message-ID: <CAOp6jLaVTk2w8Qo_syW8QhWow3vjfUd773dWoTh6n-Xj6JSHqA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: James Holderness <j4_james@hotmail.com>, www-style list <www-style@w3.org>
On Thu, Mar 21, 2013 at 11:49 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> It generally *is* a good idea to have the px be an integer number of
> device pixels.

I used to think this was true but I've come to doubt it. Firefox's
full-zoom feature almost always leads to dev-pixels-per-px being
non-integer and it seems to cause few problems. Lately we've enabled
non-integer ratios by default for Windows (7 and Metro) with high-dpi
screens and we still seem to be having few problems. I think this is true
for Firefox on Android as well, and we're in the process of configuring
FirefoxOS for high-dpi mobile devices with non-integer devicePixelRatio.

Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur
Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl
bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat
lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir
— whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb
tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28]
Received on Thursday, 21 March 2013 05:41:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:27 UTC