- From: Yoav Weiss via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Mar 2020 10:28:47 +0000
- To: public-svg-issues@w3.org
yoavweiss has just created a new issue for https://github.com/w3c/svgwg: == Request destination for SVG documents == Relevant spec section: https://svgwg.org/svg2-draft/linking.html#processingURL-fetch Related Fetch spec issue: https://github.com/whatwg/fetch/issues/1012 It's unclear which request destination fetched SVG document should have, which can impact which CSP directives control them, which `as` values developers need to set in order to preload them and which `Sec-Fetch-Dest` headers servers see in their requests. Furthermore, current implementations are use different destinations in different contexts. For example, Chrome seems to use "document" when fetching the SVG document into its own browsing context, but uses the "image" destination when the document is fetched using a `<use>` element. Please view or discuss this issue at https://github.com/w3c/svgwg/issues/782 using your GitHub account
Received on Friday, 27 March 2020 10:28:49 UTC