W3C home > Mailing lists > Public > public-canvas-api@w3.org > October to December 2013

Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath

From: Rik Cabanier <cabanier@gmail.com>
Date: Sat, 2 Nov 2013 19:03:56 -0700
Message-ID: <CAGN7qDDW1dLXRbUjpV7+Kd8ajoMuNS=FodtXk3JJT5X5k78nJA@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>
On Sat, Nov 2, 2013 at 1:01 AM, Robert O'Callahan <robert@ocallahan.org>wrote:

> On Sat, Nov 2, 2013 at 1:01 PM, Rik Cabanier <cabanier@gmail.com> wrote:
>
>> The latest Safari is shipping currentPath and Blink has implemented it
>> behind a runtime flag.
>> Could we put this in the specification?
>>
>> the proposal is for a new attribute on the 2d canvas rendering context:
>>
>> attribute Path currentPath;
>>
>>
>> This attribute would give you a non-live/copy of the current path in
>> device
>> space.
>>
>
> Does this mean that ctx.currentPath != ctx.currentPath?
>

Yes


> That's bad!
>

Why would it be bad (apart from being different)?
Received on Sunday, 3 November 2013 02:04:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:55 UTC