Re: [whatwg] Splitting CanvasRenderingContext2D

2015-12-01 Thread Ian Kilpatrick
Great, thanks all. I'll put together the start of a PR this week (just modifying the IDL) so that we can start discussing name / where everything goes. Thanks, Ian On Tue, Dec 1, 2015 at 12:11 PM, Justin Novosad wrote: > I think it may be possible to do this refactor without changing the order

Re: [whatwg] Splitting CanvasRenderingContext2D

2015-12-01 Thread Justin Novosad
I think it may be possible to do this refactor without changing the order of things since the current IDL has things grouped into categories that more or less map to what Ian is suggesting. I am currently in the middle of working on a pull request for the OffscreenCanvas propsal, and I have to say

Re: [whatwg] Splitting CanvasRenderingContext2D

2015-12-01 Thread Boris Zbarsky
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

Re: [whatwg] Splitting CanvasRenderingContext2D

2015-12-01 Thread Domenic Denicola
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Ian Kilpatrick > There are a couple of ways to split up the CanvasRenderingContext2D API, > namely adding inheritance + [NoInterfaceObject] to superclasses (as to not > change prototype chain, maybe not a large web compat concern)