W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2012

Re: [whatwg] [canvas] Path object

From: Elliott Sprehn <esprehn@gmail.com>
Date: Tue, 2 Oct 2012 16:58:06 -0700
Message-ID: <CAPJYB1jTtTLR4MxSKcR6xvmREPUfNrzKyrBG2jisQTj=C=P+2Q@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: WHATWG <whatwg@whatwg.org>
What of the fact that this breaks existing pages with <input
id="Path"> that access it as just Path? Historically this has been a
non-starter for new APIs.

On Tue, Oct 2, 2012 at 3:00 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Sat, Sep 22, 2012 at 9:17 PM, Elliott Sprehn <esprehn@gmail.com> wrote:
>> I was looking at the canvas Path API and had some concerns. In
>> particular it's inconsistent with the rest of canvas:
>>
>> We already have CanvasGradient and CanvasPattern in the global
>> namespace, so this should probably be called CanvasPath.
>>
>> We also have createLinearGradient() and createPattern(), but this new
>> thing is "new Path".
>>
>> Could we get some consistency here? Like adding new CanvasGradient()
>> (or a createPath() method) to match up with Path and renaming this
>> thing CanvasPath?
>
> I think the SVGWG would be opposed to that - we rather like the Path
> api and would appreciate being able to appropriate it for our own uses
> (merging with the <path> API).
>
> I'm fine with gradients/patterns moving to a plain constructor rather
> than a factory method, though.
>
> ~TJ
Received on Tuesday, 2 October 2012 23:59:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:10 GMT