RE: Revert request r7023

We've discussed this further and I would like to request that this change be reverted.

At this time, while the group is about to publish new heartbeat drafts, we believe that this change reduces rather than increases consensus. 
The goal of heartbeat publications is to show progress and increasing consensus. This change has been made with no discussion in the working group and no bugs filed in Bugzilla. It potentially conflicts with the change proposal for improving accessibility in canvas (ISSUE-201). We have invested a large amount of time discussing this with many members of the group before we submitted it. 

If r7023 is a counter proposal for ISSUE-201 then it should be submitted through the escalation process.

If not, then implementing the accessibility improvements described in our change proposal is a higher priority than adding features that haven't been discussed in the working group.

In either case, this change seems to be harmful to the goal of adding consensus-driven accessibility improvements to canvas.


-----Original Message-----
From: Anne van Kesteren [mailto:annevk@opera.com] 
Sent: Wednesday, March 14, 2012 1:24 PM
To: Charles Pritchard; Edward O'Connor; Frank Olivier
Cc: public-html@w3.org
Subject: Re: Revert request r7023

On Wed, 14 Mar 2012 18:18:12 +0100, Frank Olivier <Frank.Olivier@microsoft.com> wrote:
> 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.

I don't really understand this argument. What does time have to do with it?


--
Anne van Kesteren
http://annevankesteren.nl/

Received on Thursday, 15 March 2012 22:59:43 UTC