W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2015

Re: [whatwg] Splitting CanvasRenderingContext2D

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Tue, 1 Dec 2015 11:55:48 -0500
To: whatwg@lists.whatwg.org
Message-ID: <565DD114.1040109@mit.edu>
On 12/1/15 11:40 AM, Domenic Denicola wrote:
> Since it has no web-visible impact

That may or may not be true.  For example, it's quite likely to change, 
in practice, the enumeration order for properties on the obect.  Of 
course there is no spec defining that enumeration order right now... but 
in practice I believe UAs mostly do it in the IDL order.

Normally I wouldn't worry about it, but there is known content out there 
that depends on the enumeration order of _some_ things on this 
particular interface.  See 
https://bugzilla.mozilla.org/show_bug.cgi?id=631117 and 
https://bugzilla.mozilla.org/show_bug.cgi?id=623437 (note that these are 
about different URLs, though caused by the same underlying issue).

In practice I expect that an interface split that keeps arc() and 
arcTo() together in this case will be OK.  I just want to point out that 
the risk here is sadly nonzero.

Received on Tuesday, 1 December 2015 16:56:18 UTC

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