[whatwg] Processing the zoom level - MS extensions to window.screen

Glenn Maynard glenn at zewt.org
Fri Dec 31 18:43:59 PST 2010

On Fri, Dec 31, 2010 at 8:17 PM, Charles Pritchard <chuck at jumis.com> wrote:
> Nor will it be addressed, as Mozilla has given firm notice, they've intentionally obfuscated
> the value (devicePixelRatio), in the scripting environment. I dislike seeing that kind of behavior
> in any software.

It seems like the same old problem: someone's convinced himself that
he's thought of everything, and considers anything he didn't think of,
that doesn't fit the shiny, unbending, academic design in his head, as
invalid.  It's as frustrating to have my software fall victim to this
as it's always been.

Somebody wrote an NES emulator in Javascript, and even now I wouldn't
have believed it if I didn't see it myself.  Anybody saying "you
should never need to do that" today needs to prepare themselves for
plausible counterexamples.

> WebKit is stuck, as Mozilla won't budge. MS has exposed the values in a
> non-standard way.

Why is WebKit stuck because of Mozilla?  Having browser-specific fixes
for IE and for WebKit is much better than not being able to fix it at
all.  Giving a better experience to people using browsers that give me
what I need is better than forcing a broken lowest-common-denominator
on everyone.

Glenn Maynard

More information about the whatwg mailing list