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

Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Sun, 03 Nov 2013 12:29:20 +0100
To: robert@ocallahan.org
Cc: Rik Cabanier <cabanier@gmail.com>, "whatwg@whatwg.org" <whatwg@whatwg.org>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>
Message-ID: <6pcc79h47b3klfplkm0io9q9ifoal74qnk@hive.bjoern.hoehrmann.de>
* Robert O'Callahan 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.

https://mail.mozilla.org/pipermail/es-discuss/2013-October/034468.html
gives one reason.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Sunday, 3 November 2013 11:29:50 UTC

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