10023 2010-06-27 20:00:34 +0000 Behavior of 'currentColor' in CanvasRenderingContext2D poorly defined 2010-10-05 12:59:10 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML Canvas 2D Context (editor: Ian Hickson) unspecified All All RESOLVED FIXED P2 normal --- 1 andreas.kling ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 36440 0 andreas.kling 2010-06-27 20:00:34 +0000 The spec currently implies that CanvasGradient should honor the 'currentColor' value and resolve it to the canvas element's current color value at the time of assignment. If this is the case, it means that CanvasGradient objects are linked to the rendering context that created them for purposes of color resolution. This linkage should either be explicit in the spec, or removed. Personally, I don't see the use-case for supporting 'currentColor' and believe it could be removed altogether from the canvas API. 38082 1 ian 2010-08-28 04:42:21 +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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments (for CanvasGradient, anyway). 38083 2 contributor 2010-08-28 04:42:35 +0000 Checked in as WHATWG revision r5389. Check-in comment: Neuter 'currentColor' for addColorStop(), so that we don't have to track around which <canvas> created which CanvasGradient all the time. http://html5.org/tools/web-apps-tracker?from=5388&to=5389