16704 2012-04-11 22:29:47 +0000 Shouldn't there be a setClip() rather than a resetClip(). There is already a transform() and setTransform(). Shouldn't clip follow the same conventions? 2012-09-14 18:07:27 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#dom-context-2d-resetclip P3 normal Unsorted 1 contributor ian ian mike contributor oldest_to_newest 66626 0 contributor 2012-04-11 22:29:47 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html Multipage: http://www.whatwg.org/C#dom-context-2d-resetclip Complete: http://www.whatwg.org/c#dom-context-2d-resetclip Comment: Shouldn't there be a setClip() rather than a resetClip(). There is already a transform() and setTransform(). Shouldn't clip follow the same conventions? Posted from: 192.91.66.186 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.151 Safari/535.19 70702 1 contributor 2012-07-18 17:20:14 +0000 This bug was cloned to create bug 18117 as part of operation convergence. 73938 2 ian 2012-09-14 18:07:27 +0000 clip() and transform() are analogous. There's no equivalent of setTransform() for clip (you have to reset then clip), and no equivalent of resetClip() for transforms (you have to set it to the identity matrix). Given that, the current naming is consistent. One could argue that we should provide different functionality, I guess, but the current methods are based on what we expect to be common.