[whatwg] CanvasRenderingContext2D with addPath, currentPath

Robert O'Callahan robert at ocallahan.org
Sat Nov 2 20:11:08 PDT 2013

On Sun, Nov 3, 2013 at 3:03 PM, Rik Cabanier <cabanier at gmail.com> wrote:

> On Sat, Nov 2, 2013 at 1:01 AM, Robert O'Callahan <robert at 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

More information about the whatwg mailing list