a very small feature that i'm unreasonably excited about: referencing a whole `.svg` (rather than just a fragment).
```
<use href="thing.svg">
```
shipped in chrome 137: https://chromestatus.com/feature/5128141573718016
but safari is stalling for no good reason: https://github.com/WebKit/standards-positions/issues/480
@rawrmonstar i just want to use any svg without having to mess with its internal code.
@mayank Chrome <del>invents a web feature, does not go through standardization</del> <ins>moves forward with implementing an editor draft change</ins>, there are ongoing security concerns, but WebKit is stalling, because they did not jump to an implementation within 8 weeks? Come on.
TAG only reviewed it a month ago: https://github.com/w3ctag/design-reviews/issues/1081
Just a little patience, please.
こんにちは TAG-さん! 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 eleme...
@yatil ??
this has been in the SVG2 spec for a long time. https://svgwg.org/svg2-draft/struct.html#UseElement
edit: better link https://www.w3.org/TR/SVG2/struct.html#UseElement
@mayank The SVG specification is weird, it is linked from the SVG rec[1] but this is clearly an editors draft. Anyway, it’s Chrome’s timeline for implementation, and that doesn’t mean that another vendor (FFx seems to also not implement yet) stalls for not immediately jumping to it.
@yatil i'm not asking for them to "jump to an implementation". just very disappointed in their position.
if it's "harmless" then why not support it instead of leaving it in limbo?
@mayank Not one to defend WebKit unnecessarily but "SVG is very poorly specced and we should probably be working towards fixing that before implementing new stuff" does seem to be a good reason to me...
Having worked on stuff that touched SVG (Trusted Types) it's a pain not having any proper spec for it.
@Lukew would a better spec make a difference for this particular feature? if yes, is webkit going to help with improving the spec and *then* support this feature?
my fear is this is going to stay unresolved like this for many years, which is arguably much worse than before chrome implemented it.
@mayank Arguably chrome touched it last so chrome should invest some money into fixing it. Frankly they're both mega corps and should be spending far more on resolving these issues. But something that's small and harmless in isolation isn't necessarily harmless in totality.
Doing small "oh this just builds on the flaming mattress" additions doesn't help actually put out the mattress.
Olliew
Mayank
Tegan
Eric Eggert
jake lazaroff
Luke
Scott Kellum 
Zacky Ma