- From: David Storey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Apr 2018 20:52:08 +0000
- To: public-svg-issues@w3.org
@prlbr it doesn`t really matter if HTML or SVG does a better job; a lot more developers know HTML than SVG and so would be the most expected behaviour. The DOM would be consistent is we went with src but indeed the tag name would be different. If it is possible to use src then perhaps we could look at aliasing img/image like HTML does. @AmeliaBR that is unfortunate :( (another case of non-standard usage biting us). Do we have any data on if that technique is actually popular or if it is just a few early adopters? We can't use the normal detecting if SVGImageElement.src is in use cause that of course is not supported. ChromeStatus is broken for me right now (showing an empty list) and I don't recall if it shows Content attribute usage or just IDL attributes. Although it probably isn't measured anyway with it being non-standard usage. I have fallen for the lack of src on SVGScriptElement myself recently (I assumed that was why the test case template uses html:script rather than SVG scripts until I looked at the spec and saw the href mixin. It would be kind of weird to fix script but not image though. -- GitHub Notification of comment by dstorey Please view or discuss this issue at https://github.com/w3c/svgwg/issues/410#issuecomment-381745275 using your GitHub account
Received on Monday, 16 April 2018 20:52:12 UTC