17427 2012-06-05 20:25:39 +0000 <canvas>: drawImage() should accept SVGImageElement (<svg:image>) 2016-03-18 08:54:47 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED http://www.whatwg.org/specs/web-apps/current-work/#2dcontext P3 enhancement Needs Impl Interest 1 contributor ian annevk bzbarsky cabanier cam d dtrebbien ian junov junov mike contributor oldest_to_newest 68744 0 contributor 2012-06-05 20:25:39 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html Multipage: http://www.whatwg.org/C#2dcontext Complete: http://www.whatwg.org/c#2dcontext Comment: drawImage should accept SVGImageElement Posted from: 71.184.125.56 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1 68745 1 bzbarsky 2012-06-05 20:26:10 +0000 We're trying to converge <hgml:img> and <svg:image> as much as we can, as I understand. 70907 2 contributor 2012-07-18 17:43:49 +0000 This bug was cloned to create bug 18220 as part of operation convergence. 74164 3 ian 2012-09-20 21:41:43 +0000 Is there a spec I can point to that defines the <svg:image> processing model? The stuff like "available", interaction with the network, CORS, event loop, etc? 74320 4 cam 2012-09-23 01:25:40 +0000 No, but if you can tell me the list of things that I need to define (and what terms to link to from the HTML spec) I'll do the SVG spec changes needed. 78766 5 ian 2012-11-25 05:17:32 +0000 I don't know exactly what it needs, but here's the equivalent section for the <img> element in HTML: http://www.whatwg.org/specs/web-apps/current-work/#the-img-element The stuff I need for drawImage() specifically is the same stuff as what I need for ImageBitmap, which may be easier to isolate — see the section that says "If image is an img element" here: http://www.whatwg.org/specs/web-apps/current-work/#images ...specifically, the equivalents of: "completely available" "origin" "media data" 83904 6 cabanier 2013-03-02 22:19:22 +0000 (In reply to comment #5) > I don't know exactly what it needs, but here's the equivalent section for > the <img> element in HTML: > > http://www.whatwg.org/specs/web-apps/current-work/#the-img-element > > The stuff I need for drawImage() specifically is the same stuff as what I > need for ImageBitmap, which may be easier to isolate — see the section that > says "If image is an img element" here: > > http://www.whatwg.org/specs/web-apps/current-work/#images > > ...specifically, the equivalents of: > > "completely available" > "origin" > "media data" I'm not sure that this is needed. The svgsvgelement [1] is like the HTML canvas. The element and all of its descendant are part of the document and available. 1: http://www.w3.org/TR/SVG/struct.html#InterfaceSVGSVGElement 86085 7 ian 2013-04-12 22:01:37 +0000 We're not talking about <svg:svg>, we're talking about <svg:image>. 86088 8 cabanier 2013-04-12 22:27:27 +0000 (In reply to comment #7) > We're not talking about <svg:svg>, we're talking about <svg:image>. I didn't catch that. I don't think there's a big demand for such a feature. 125538 9 annevk 2016-03-16 17:43:30 +0000 bz, it seems this didn't get the interest we need to add this to HTML. Let me know if you want me to reconsider. 125539 10 d 2016-03-16 17:45:27 +0000 +junov just in case Chrome is interested in this. 125551 11 bzbarsky 2016-03-16 18:57:36 +0000 My understanding is that the SVG working group is actively trying to converge its "duplicated" elements with the corresponding HTML ones. Given that, it seems like we should treat them identically; pretty much anything else is rather author-hostile. In particular, it seems to me that <svg:image> should use the same processing model as <html:img> and hence this should all be quite straightforward to spec. And probably implement; in Gecko all the logic is shared and hence the work to support <svg:image> here is tiny; I would be surprised if it's very different in other browsers. 125553 12 annevk 2016-03-17 04:56:14 +0000 Okay, happy to reconsider. I guess we could check all the places that accept HTMLImageElement and make them accept SVGImageElement too. I don't think we necessarily need to wait on SVG to sort out their standard if we all know it's supposed to work identically (though we should maybe point that out with a note until things are sorted). Justin, what do you think? 125562 13 junov 2016-03-17 19:20:41 +0000 Yes, I think this makes sense. To match use cases of HTMLImageElement, I think we should add SVGImageElement to the CanvasImageSource and ImageBitmapSource typedefs, which implies supporting it as an argument to drawImage, createPattern and createImageBitmap. 125563 14 annevk 2016-03-18 08:54:47 +0000 Created a pull request: https://github.com/whatwg/html/pull/900.