11739 2011-01-11 22:51:44 +0000 <canvas>: clearPath() that clears pixels the way clearRect() does, but using a path 2014-09-26 21:31:31 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#dom-context-2d-clearrect P3 enhancement Needs Impl Interest 9236 1 contributor ian ian jackalmage mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 44243 0 contributor 2011-01-11 22:51:44 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#complex-shapes-(paths) Comment: I would like to see a clearPath or clearStroke functions similar to clearRect but to clear lines, not just full rectangles Posted from: 71.9.39.98 44245 1 jackalmage 2011-01-11 23:00:52 +0000 This can be achieved currently by making a path, calling clip(), *then* calling clearRect with a bounding rectangle specified. That technique is fairly unintuitive, though. A clear() method that clears out a path would be nice. 45357 2 ian 2011-02-11 01:27:04 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: That might make sense, but in a future version. 45364 3 ian 2011-02-11 01:33:19 +0000 > Change Description: see diff given below That should read "none yet", my apologies. 52678 4 mike 2011-08-04 05:03:35 +0000 mass-move component to LC1 64766 5 ian 2012-02-29 22:11:36 +0000 What's the use case for this, exactly? Having played with canvas quite a bit recently I've never found myself needing anything but clearRect() applied to the entire canvas... 64767 6 jackalmage 2012-02-29 22:16:00 +0000 I've used the technique I outlined in Comment #1 for a Worms-like game before. When your gun hit, I did a clearRect() (clipped to a path) to remove pixels from the "level" canvas. 64781 7 ian 2012-02-29 22:45:06 +0000 I guess that makes sense. So basically this is just a shorthand for: .save(); .clip(); .setTranform(identity) .clearRect(entire canvas) .restore(); ...? 64782 8 jackalmage 2012-02-29 22:46:39 +0000 Yup. 64789 9 ian 2012-02-29 22:54:52 +0000 I'm going to punt on this for now, and review it at a later date to see how much demand there has been for it. So far it seems like it would be little more than a convenience method and I haven't heard much demand for it. 82059 10 mike 2013-01-24 07:38:04 +0000 This bug was cloned to create HTML WG bug 19026. 84674 11 ian 2013-03-19 22:56:28 +0000 Any implementation interest on this? How compelling a use case is it? If it's not needed by many people, since it's only a convenience API essentially, maybe it's not worth doing? 112320 12 ian 2014-09-26 21:31:31 +0000 Marking WONTFIX since it's gotten no vendor interest and it's equivalent to five lines of simple code anyway.