<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 20, 2010, at 7:46 AM, Ojan Vafai wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div class="gmail_quote">On Fri, Nov 19, 2010 at 9:21 PM, Robert O'Callahan <span dir="ltr"><<a href="mailto:robert@ocallahan.org">robert@ocallahan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div class="im">Most of the use cases for script access to the exact device pixel ratio that I've heard boil down to "interfere with the user's ability to zoom", which is why I haven't been eager to make it easier.</div>
</blockquote><div class="gmail_quote"><br></div>To be clear, <span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">chrome.tabs.getZoomPercentage is a Chrome extension API. Having extensions that can mess with zoom seems like a legit use-case. But I agree, I can't think of good use-cases for the general web being able to.</span></div></div></blockquote><br></div><div>The only one I can think of is sizing the canvas backing store to get a sharp image on high-resolution displays, and possibly swapping in different image assets from JS.</div><div><br></div><div>Simon</div><div><br></div></body></html>