- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 Apr 2018 16:45:17 +0000
- To: public-svg-issues@w3.org
I think [this was the last discussion thread, from waaay back in 2015, when discussions were on the mailing list](https://lists.w3.org/Archives/Public/www-svg/2015Apr/0029.html). For `<image>`, switching to `src` would break a commonly used fallback approach: ```html <svg><image src="icon.png" xlink:href="icon.svg" width="16" height="16"/></svg> ``` (An `<image>` outside of `<svg>`, or in a browser that doesn't support inline SVG, is treated as a synonym of `<img>` in HTML.) I personally think that adding `srcset` is much more useful moving forward, (see #208). It's possible that authors were using the same trick for `<script>` to load different scripts depending on whether SVG is supported or not, although I'm not familiar with any examples. But it also didn't make much sense to change `<script>` if we weren't going to change `<image>`. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/410#issuecomment-381420369 using your GitHub account
Received on Sunday, 15 April 2018 16:45:21 UTC