- From: Fredrik Söderqvist via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Dec 2019 22:09:36 +0000
- To: public-svg-issues@w3.org
What Chromium does here has nothing to do with the SVG spec having been interpreted literally or not. I think what is observed in that case is an implementation of the HTML `<canvas>` spec [1]. > If the sx, sy, sw, and sh arguments are omitted, then they must default to 0, 0, the image's intrinsic width in image pixels, and the image's intrinsic height in image pixels, respectively. The image in the bug has an intrinsic width of 100 and an intrinsic height of 100. So a rectangle of 0,0,100,100 from the source is drawn to the specified destination rectangle. So I guess Chromium is pretty literal on interpreting the HTML `<canvas>` spec, but I don't think that has anything to do with the interpretation (or quality) of the current SVG spec text. Do I think that the HTML `<canvas>` spec makes sense here? No, not really. [1] https://html.spec.whatwg.org/multipage/canvas.html#drawing-images:dom-context-2d-drawimage-3 -- GitHub Notification of comment by fsoder Please view or discuss this issue at https://github.com/w3c/svgwg/issues/762#issuecomment-563463255 using your GitHub account
Received on Monday, 9 December 2019 22:09:37 UTC