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 20:42:45 -0700
Message-ID: <CAGN7qDAaT0-FOO0VA9OcNY1LMp=AihtcpivnmvOjGmkEPquJDQ@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 8:11 PM, Robert O'Callahan <robert@ocallahan.org>wrote:

> 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.
>

Maybe we should revisit this design principle or be less strict. It feels
unnatural to give access to internal objects.
Isn't this also part of the reason that we now have 3 different interfaces
for DOMRect and DOMMatrix?
Received on Sunday, 3 November 2013 03:43:14 UTC

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