Open
Bug 1865837
Opened 1 year ago
Updated 3 months ago
Should SVG's `<image>` element support the `fetchpriority` attribute analogous to HTML's `<img>` element?
Categories
(Core :: Graphics: ImageLib, enhancement)
Core
Graphics: ImageLib
Tracking
()
ASSIGNED
People
(Reporter: mbrodesser-Igalia, Assigned: fredw)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #1847712 +++
Reporter | ||
Updated•1 year ago
|
Updated•1 year ago
|
Component: Networking → Graphics: ImageLib
Updated•1 year ago
|
Severity: -- → S3
Assignee | ||
Comment 1•9 months ago
|
||
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 the
fetchpriority`
attributes (see https://github.com/w3c/svgwg/issues/925) so the internal
priority should remain the same when the flag is enabled.
Updated•9 months ago
|
Assignee: nobody → fwang
Status: NEW → ASSIGNED
Assignee | ||
Updated•9 months ago
|
Keywords: leave-open
Pushed by fwang@igalia.com:
https://hg.mozilla.org/integration/autoland/rev/ba8d0b7f1a2a
Add fetchpriority test for SVG <image> element. r=valentin,necko-reviewers
Comment 3•9 months ago
|
||
bugherder |
Comment 4•3 months ago
|
||
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.
Flags: needinfo?(tnikkel)
Updated•3 months ago
|
Flags: needinfo?(tnikkel)
Updated•3 months ago
|
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•