On 11/20/10 3:59 PM, Charles Pritchard wrote:
This response is from the digest: I'm glad to see activity here.
Canvas is supposed to be resolution independent,
No, it's not. Vector images are supposed to be resolution independent.
Canvas is very explicitly a _bitmap_. It's not a vector imag
Depending on how the Path object gets implemented, there could be a lot more
benefits. E.g. the Context could be transformed without transforming the path.
It would be possible to get a point at a given length on a path or the path
length itself. It would be possible to get a segment on a path o
This response is from the digest: I'm glad to see activity here.
As I can't figure out how to hit reply in thread, I'll take some editorial
discretion here and just summarize it, so we can make a decision on the
use case.
Ojan calls for: "good use-cases for the general web",
Boris implies that
On Sat, Nov 20, 2010 at 9:49 AM, Simon Fraser wrote:
> On Nov 20, 2010, at 7:46 AM, Ojan Vafai wrote:
> To be clear, 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
On Nov 20, 2010, at 7:46 AM, Ojan Vafai wrote:
> On Fri, Nov 19, 2010 at 9:21 PM, Robert O'Callahan
> wrote:
> 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
On Fri, Nov 19, 2010 at 9:21 PM, Robert O'Callahan wrote:
> 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.
>
To be clear, chrome.tabs.getZoom
