- From: Charles Pritchard <chuck@jumis.com>
- Date: Fri, 16 Mar 2012 14:35:48 -0700
- To: Anne van Kesteren <annevk@opera.com>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, HTML WG <public-html@w3.org>
On 3/16/2012 2:22 PM, Anne van Kesteren wrote: > On Fri, 16 Mar 2012 21:46:40 +0100, Tab Atkins Jr. > <jackalmage@gmail.com> wrote: >> At the request of the chairs, I'd like to reiterate my opposal to >> reverting this. Same reasons as before. > > To make it more explicit, I also object to reverting this per prior > given arguments. Anne, are these the arguments for keeping the HTML Path authored by Hixie? Tab: "The Path object being added to the spec right now is a result of addressing many bugs asking for added canvas functionality since the last time Hixie touched that part of the spec. Presumably if the simpler CanvasPath addressed the use-cases implied by the bugs he's addressing, he would have used it. Simpler's usually better, after all." Ted: "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." Anne: "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" I've provided counter-arguments to these points, but it seems my counter-arguments have fallen flat. In practice, I think implementers will repeat my recommendations, because they're simple relative to the HTML Path proposal. Regardless of this revert, we can cut out the massive IDL change and keep some of the verbiage. -Charles
Received on Friday, 16 March 2012 21:36:09 UTC