- From: Charles Pritchard <chuck@jumis.com>
- Date: Fri, 16 Mar 2012 10:22:33 -0700
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Edward O'Connor <eoconnor@apple.com>, Frank Olivier <Frank.Olivier@microsoft.com>, "public-html@w3.org" <public-html@w3.org>
On Mar 16, 2012, at 1:02 AM, "Anne van Kesteren" <annevk@opera.com> wrote: >> This change has been made with no discussion in the working group and no bugs filed in Bugzilla. > > I clearly remember discussing this in person with you at TPAC. Our rather poor minutes of that meeting even captured it: http://www.w3.org/2011/11/03-html-wg-minutes Those minutes are mostly about Canvas a11y; the changes in discussion off no a11y solutions not progress. A reusable Canvas Path object means a (very slight) speed up in redrawing as the implementation can keep some basic calculations around. Very slight. The change put forward by the editor doesn't address accessibility nor is it designed to optimize the efficiency of Canvas rendering. It is a broad change, instead, to the Canvas 2D context in an attempt to implement Doug's "COG" proposal. I don't understand why Ted or Anne think this change set is something else. The change is very broad. If the editor were addressing the TPAC conversation, it would have been done with a minimum of changes. Such as: ctx.addEventTarget(element); // bind current path to subelement forwarding pointer events for hit testing. path = ctx.createPath(); // create an opaque path object for re-use in drawing commands. -Charles
Received on Friday, 16 March 2012 17:23:03 UTC