<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/21/2010 4:12 PM, Robert O'Callahan wrote:
<blockquote
cite="mid:AANLkTinaVhpmbWR7dFBMM6iDPwBtx25nRTjO7BfG_egQ@mail.gmail.com"
type="cite">On Sun, Nov 21, 2010 at 9:59 AM, Charles Pritchard <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:chuck@jumis.com">chuck@jumis.com</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Rob: Mobile deployments using dpiPixelRatio (as has been
adopted by Moz and Webkit) and target-DpiDensity work well on
the mobile, they are not hooked to zoom on the desktop,<br>
</blockquote>
<div><br>
It is in Firefox.<br>
</div>
</div>
</blockquote>
I just tested in 4b7, and it's not changing dpiPixelRatio.<br>
<br>
I'm still at a loss on why exposing additional metrics in
window.screen is distasteful.<br>
You currently expose availWidth/availHeight, etc.<br>
<br>
I'm not saying this to discount your proposals, or distract from
dpiPixelRatio as a viable option.<br>
<br>
Why is exposing more properties to window.screen is a non-starter?<br>
<br>
MS has already opened it up; webkit devs may have some opinions on
it, and I'll let you know when I hear them.<br>
<br>
<a
href="http://msdn.microsoft.com/en-us/library/ms535868%28VS.85%29.aspx">http://msdn.microsoft.com/en-us/library/ms535868(VS.85).aspx</a><br>
<br>
I agree it may not be a 20-year solution, but it could certainly
work for this generation of browsers.<br>
It doesn't *need* to be a Canvas-use case. As I've stated, it could
apply just as well to images.<br>
<br>
-Charles<br>
<br>
<br>
</body>
</html>