1865837 - Should SVG's `<image>` element support the `fetchpriority` attribute analogous to HTML's `<img>` element?

Status: RESOLVED FIXED

(Core :: Graphics: ImageLib, enhancement)

Description

[Mirko Brodesser (:mbrodesser) -- not reading bugmails currently]

+++ This bug was initially created as a clone of Bug #1847712 +++

Comment 1

[Frédéric Wang (:fredw)]

Attachment: Bug 1865837 - Add fetchpriority test for SVG <image> element. r=valentin,#necko-reviewers

When network.fetchpriority is disabled, it is expected that SVG
<image> elements use the same internal priority as <img> elements. Currently,<image>elements do not support thefetchpriority`
attributes (see https://github.com/w3c/svgwg/issues/925) so the internal
priority should remain the same when the flag is enabled.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ba8d0b7f1a2a
Add fetchpriority test for SVG <image> element. r=valentin,necko-reviewers

Comment 3

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/ba8d0b7f1a2a

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The leave-open keyword is there and there is no activity for 6 months.
:tnikkel, maybe it's time to close this bug?
For more information, please visit BugBot documentation.

Comment 5

[Robert Longson [:longsonr]]

Fixed by checkin for bug 1847712

Comment 6

[Sebastian Zartner [:sebo]]

This should be documented and the related browser compat data be added.

Sebastian