I'm requesting a TAG review of "Allow use to reference an external document's root element by omitting the fragment".
The use element in SVG allows for the reuse of existing SVG elements by referencing them, but currently browsers only support these being id references. We propose that browsers also support the SVG2 capability of allowing a use reference to refer to an entire SVG file, without id.
User research: Developers using external SVGs in their projects have shown interest for this feature. Please refer to the explainer document for further details about their use cases.
Security and Privacy self-review²: Non-applicable (Resolution for this spec is already achieved and we are raising this TAG review to inform that Chromium is ready to adapt this specification)
Primary contacts:
Divyansh Mangal (@goldenboy777), Microsoft.
Ragvesh Sharma (@Ragvesh-Sharma), Microsoft.
Abhishek Singh (@abhishek06020), PM, Microsoft.
Organization/project driving the specification: Microsoft
Relevant time constraints or deadlines: April, 2025
You should also know that...
This specification is already resolved and available in the SVG2. As per Chromium guidelines, since none of the browsers has currently implemented this specification, https://www.chromium.org/blink/launching-features/wide-review/#exceptions, we are raising this TAG issue to review this spec and to announce that Chromium/blink is ready to adapt this as a feature.
<!------------------------------------------------------------------------------------
CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING
Use links to content rather than pasting text into this issue. Issues are ephemeral and most of the material we are asking for has long term value.
Please preview the issue and check that the links work before submitting. Please make sure anyone with the link can access the document. We may refuse to review anything that is not public.
¹ We require an explainer to give the relevant context for the spec review, even if the spec has some background information. An explainer must address user needs and contain examples of use. For more information, see our [explanation of how to write a good explainer](https://tag.w3.org/explainers/).
² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.
³ For your own organization, you can simply state the organization's position instead of linking to it. This includes items on [Mozilla standards-positions](https://github.com/mozilla/standards-positions), and [WebKit standards-positions](https://github.com/WebKit/standards-positions). Chromium doesn't have a standards-positions repository and [prefers](https://source.chromium.org/chromium/chromium/src/+/main:docs/standards/positions/GoogleChrome/README.md) to use comments from the teams that maintain the relevant area of their codebase.
⁴ Include links to [Chrome Status](https://chromestatus.com/), [Mozilla's](https://bugzilla.mozilla.org/), [WebKit's Bugzilla](https://bugs.webkit.org/), and trackers for other implementations if those are known to you.
-->
OpenedApr 15, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of "Allow use to reference an external document's root element by omitting the fragment".
The
useelement in SVG allows for the reuse of existing SVG elements by referencing them, but currently browsers only support these being id references. We propose that browsers also support the SVG2 capability of allowing ausereference to refer to an entire SVG file, without id.Explainer¹: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/SVG/allow-use-to-reference-entire-files.md
Specification: https://svgwg.org/svg2-draft/struct.html#UseElement
User research: Developers using external SVGs in their projects have shown interest for this feature. Please refer to the explainer document for further details about their use cases.
Security and Privacy self-review²: Non-applicable (Resolution for this spec is already achieved and we are raising this TAG review to inform that Chromium is ready to adapt this specification)
Primary contacts:
Organization/project driving the specification: Microsoft
This work is being funded by: Microsoft
Primary standards group developing this feature: W3C SVG Working Group
Incubation and standards groups that have discussed the design:
Multi-stakeholder support³:
Further details:
You should also know that...
This specification is already resolved and available in the SVG2. As per Chromium guidelines, since none of the browsers has currently implemented this specification, https://www.chromium.org/blink/launching-features/wide-review/#exceptions, we are raising this TAG issue to review this spec and to announce that Chromium/blink is ready to adapt this as a feature.
<!------------------------------------------------------------------------------------ CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING Use links to content rather than pasting text into this issue. Issues are ephemeral and most of the material we are asking for has long term value. Please preview the issue and check that the links work before submitting. Please make sure anyone with the link can access the document. We may refuse to review anything that is not public. ¹ We require an explainer to give the relevant context for the spec review, even if the spec has some background information. An explainer must address user needs and contain examples of use. For more information, see our [explanation of how to write a good explainer](https://tag.w3.org/explainers/). ² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/. ³ For your own organization, you can simply state the organization's position instead of linking to it. This includes items on [Mozilla standards-positions](https://github.com/mozilla/standards-positions), and [WebKit standards-positions](https://github.com/WebKit/standards-positions). Chromium doesn't have a standards-positions repository and [prefers](https://source.chromium.org/chromium/chromium/src/+/main:docs/standards/positions/GoogleChrome/README.md) to use comments from the teams that maintain the relevant area of their codebase. ⁴ Include links to [Chrome Status](https://chromestatus.com/), [Mozilla's](https://bugzilla.mozilla.org/), [WebKit's Bugzilla](https://bugs.webkit.org/), and trackers for other implementations if those are known to you. -->