This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.w3.org/TR/2dcontext/ Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top Comment: var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); Posted from: 113.162.168.144
Wouldn't it make more sense to support passing an <svg> node to drawImage?
(In reply to comment #1) > Wouldn't it make more sense to support passing an <svg> node to drawImage? Opera supports that, FWIW.
So does Gecko.
Time to spec it?
What are the intrinsic dimensions of an <svg> node? What should it render, exactly? e.g. what time should it use for animations, should filters that are based on content outside the <svg> be recomputed, should any scripts or events run? See also bug 11488.
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: Did Not Understand Request Change Description: no spec change Rationale: Without solid answers to the questions in comment 5, I'm not sure what to do here.
mass-move component to LC1