W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2013

Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 2 Nov 2013 21:01:43 +1300
Message-ID: <CAOp6jLar64D7AJkNxEBeTSrJQhZ_hspdRQr4udSimqtpS+U4+Q@mail.gmail.com>
To: Rik Cabanier <cabanier@gmail.com>
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 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? That's bad!

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
Received on Saturday, 2 November 2013 08:02:10 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:13 UTC