[whatwg] CanvasRenderingContext2D with addPath, currentPath
cabanier at gmail.com
Sat Nov 2 20:42:45 PDT 2013
On Sat, Nov 2, 2013 at 8:11 PM, Robert O'Callahan <robert at ocallahan.org>wrote:
> 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?
>>> 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?
More information about the whatwg