-
Notifications
You must be signed in to change notification settings - Fork 23k
Firefox 147 supports media fragments in SVG URLs #42348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Firefox 147 supports media fragments in SVG URLs #42348
Conversation
|
Preview URLs External URLs (1)URL:
(comment last updated: 2025-12-15 13:23:53) |
|
I would say if we have non-standard Firefox-only |
@pepelsbey OK, I guess so. But, where to put it? In terms of both content and BCD? It is a type of URL fragment, which leads me to think maybe I could put it next to the text fragment docs, here: https://developer.mozilla.org/en-US/docs/Web/URI/Reference/Fragment. In terms of BCD, I'm really not sure. It can be used anywhere where an SVG can be used as an image, like |
…avidmills/content into fx147-media-fragments-in-svg-urls
|
@pepelsbey OK, I've added a page covering media fragment syntax, and linked to it from the rel notes instead of the spec. Let me know what you think. As you'll see, I've included a hand-written browser compat section, with a few useful notes on what I found when I did some (relatively) extensive testing. I'm not convinced it is worth my while trying to create comprehensive browser compatibility data for this feature, as it would be long-winded and painful ;-/ |
Description
Firefox 147 adds support for media fragment syntax when using SVG files as image sources. See https://bugzilla.mozilla.org/show_bug.cgi?id=1999989.
This PR adds a rel note to cover this addition.
I've not added any other content covering this functionality, because it is a very general feature that otherwise has no support (except for temporal syntax on
<video>/<audio>sources), and to add information about it just for one browser in one specific context seems weird. You could argue that it's the kind of information that belongs in BCD, but we don't really have anywhere to record BCD for a feature like this.Let me know if you disagree with this. I'd appreciate a second opinion.
Motivation
Additional details
Related issues and pull requests