- From: David Storey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 May 2018 00:30:29 +0000
- To: public-svg-issues@w3.org
dstorey has just created a new issue for https://github.com/w3c/svgwg: == Consider adding decoding and decode to SVGImageElement == HTML defines the decoding attribute and decode() method on HTMLImageElement. https://html.spec.whatwg.org/multipage/embedded-content.html#the-img-element Chrome implements both of these on SVGImageElement: https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/svg/svg_image_element.idl Do we want to standardize that? If so it would probably be best to work with HTML to make a HTMLOrSVGImageElement mixin (or a different name as that is taken by a typedef) with these two and crossOrigin (that we already define in SVG) and possibly referrerPolicy (Firefox has added it to SVGAElement already, so that would be consistent). As the mixin would be in HTML it would be defined in that spec what got added so we wouldn't have to worry about what members are implemented for SVG 2 CR/REC. Please view or discuss this issue at https://github.com/w3c/svgwg/issues/444 using your GitHub account
Received on Friday, 11 May 2018 00:30:33 UTC