W3C home > Mailing lists > Public > public-html@w3.org > March 2012

RE: Revert request r7023

From: Frank Olivier <Frank.Olivier@microsoft.com>
Date: Wed, 14 Mar 2012 17:18:12 +0000
To: Charles Pritchard <chuck@jumis.com>, Edward O'Connor <eoconnor@apple.com>
CC: "public-html@w3.org" <public-html@w3.org>
Message-ID: <91175A762AB48840AF1473514B26B47552845646@TK5EX14MBXC262.redmond.corp.microsoft.com>
We currently have no plans to add Path support. We're concerned that adding this feature to the canvas 2d API spec at this time increases web developer confusion about which parts of the spec are stable and interoperable.

For ISSUE-201, we have already made a proposal (that was created with input from others in the canvas and a11y WGs) which we wish to support in IE.

-----Original Message-----
From: Charles Pritchard [mailto:chuck@jumis.com] 
Sent: Wednesday, March 14, 2012 9:41 AM
To: Edward O'Connor
Cc: public-html@w3.org
Subject: Re: Revert request r7023

I encourage vendors to act by assigning resources to produce actionable implementations. Waiting and/or following the invention of the editor is a bit backwards.

His strength is in identifying APIs common across vendors and writing them up in his document.

I've stated my concerns; I withdraw my revert request. The "bugs" in this change to Canvas are public. I'm going to work on implementation instead of pursuing bug reports and process.

-Charles

On Mar 14, 2012, at 8:35 AM, Edward O'Connor <eoconnor@apple.com> wrote:

> Hi,
> 
> Charles wrote:
> 
>> I'm concerned that the change will create undo burden on implementers 
>> and authors. A much simpler change set was proposed last year and has 
>> not been addressed by the editor.
>> 
>> It's my contention that the editor's "Path" object, as it is 
>> authored, is not appropriate for Canvas 2D but may be appropriate for 
>> SVG2[…]
> 
> We oppose this revert request. We've been advocating for the addition 
> of an exposed Path object to the <canvas> 2D Context API for a long 
> time—it greatly improves the general utility of the 2D Context API, in 
> addition to its obvious accessibility benefits.
> 
> I encourage other vendors supportive of this change to also speak up.
> 
> As Steve Faulkner said, Charles,
>> I would suggest the best way forward is to file bugs against the spec 
>> and then follow the usual escalation process if needed.
> 
> 
> Ted
> 


Received on Wednesday, 14 March 2012 17:19:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:30 UTC