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

Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sun, 3 Nov 2013 16:11:08 +1300
Message-ID: <CAOp6jLY35WVAkDEPuR9wmnjsUuOpqNMbgMoy5s4+6USZDamCqQ@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 Sun, Nov 3, 2013 at 3:03 PM, Rik Cabanier <cabanier@gmail.com> wrote:

> On Sat, Nov 2, 2013 at 1:01 AM, Robert O'Callahan <robert@ocallahan.org>wrote:
>> Does this mean that ctx.currentPath != ctx.currentPath?
> Yes
>>  That's bad!
> Why would it be bad (apart from being different)?

It means that currentPath isn't behaving anything like a data member.

I'm not super familiar with why this became such an important design
principle, but I know that it is one. For example, this is exactly the
reason why the WebIDL spec prohibits attributes from returning dictionaries.

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 Sunday, 3 November 2013 03:11:34 UTC

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