Skip to content

Conversation

@chrisdavidmills
Copy link
Contributor

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

@chrisdavidmills chrisdavidmills requested a review from a team as a code owner December 11, 2025 08:44
@chrisdavidmills chrisdavidmills requested review from bsmth and pepelsbey and removed request for a team December 11, 2025 08:44
@github-actions github-actions bot added Content:Firefox Content in the Mozilla/Firefox subtree size/s [PR only] 6-50 LoC changed labels Dec 11, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 11, 2025

Preview URLs

External URLs (1)

URL: /en-US/docs/Mozilla/Firefox/Releases/147
Title: Firefox 147 release notes for developers (Beta)

(comment last updated: 2025-12-15 13:23:53)

@pepelsbey
Copy link
Member

I would say if we have non-standard Firefox-only element() CSS function documented, then we should definitely have docs for standard features like these.

@chrisdavidmills
Copy link
Contributor Author

I would say if we have non-standard Firefox-only element() CSS function documented, then we should definitely have docs for standard features like these.

@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 <img>, background-image, HTMLImageElement.src/<canvas>, various SVG elements, etc. Potentially we could put a subfeature inside every single one, which seems a bit odd to me. WDYT?

@chrisdavidmills chrisdavidmills requested a review from a team as a code owner December 15, 2025 13:22
@github-actions github-actions bot added Content:Other Any docs not covered by another "Content:" label size/m [PR only] 51-500 LoC changed and removed size/s [PR only] 6-50 LoC changed labels Dec 15, 2025
@chrisdavidmills
Copy link
Contributor Author

@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 ;-/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Content:Firefox Content in the Mozilla/Firefox subtree Content:Other Any docs not covered by another "Content:" label size/m [PR only] 51-500 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants