- From: Edward O'Connor <eoconnor@apple.com>
- Date: Tue, 20 Mar 2012 13:16:03 -0700
- To: public-html@w3.org
Frank wrote: > We've discussed this further and I would like to request that this > change be reverted[…] It potentially conflicts with the change > proposal for improving accessibility in canvas (ISSUE-201). I don't think the changes in r7023 directly conflict with your proposal. The context object has an implicit current path and exposes several "Path-y" methods which act on the current path. If hit testing methods are defined in an interface implemented by both the context object and by Path objects, then your implementation could ship those methods only on the context object if it doesn't ship an exposed Path object. > 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. Adding an exposed Path object to the <canvas> 2D Context API has come up several times in this Working Group over a long period of time. Ted
Received on Tuesday, 20 March 2012 20:16:38 UTC