Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should SVG's <image> element support the fetchpriority attribute analogous to HTML's <img> element? #925

Open
mbrodesser-Igalia opened this issue Nov 21, 2023 · 1 comment
Open

Should SVG's <image> element support the fetchpriority attribute analogous to HTML's <img> element? #925

mbrodesser-Igalia opened this issue Nov 21, 2023 · 1 comment

Comments

@mbrodesser-Igalia
Copy link

https://svgwg.org/svg2-draft/embedded.html#ImageElement
https://html.spec.whatwg.org/multipage/embedded-content.html#the-img-element

See also #916.
@foolip
Copy link
Member

foolip commented Dec 8, 2023

I've asked @pmeenan about this and we thing this would be a nice-to-have, but not high priority.

moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue Feb 15, 2024
@fred-wang
Bug 1865837 - Add fetchpriority test for SVG <image> element. r=valen…
61f7e00 
…tin,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 the `fetchpriority`
attributes (see w3c/svgwg#925) so the internal
priority should remain the same when the flag is enabled.

Differential Revision: https://phabricator.services.mozilla.com/D201385
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this issue Feb 16, 2024
@marco-c
Bug 1865837 - Add fetchpriority test for SVG <image> element. r=valen…
a63cfdf 
…tin,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 the `fetchpriority`
attributes (see w3c/svgwg#925) so the internal
priority should remain the same when the flag is enabled.

Differential Revision: https://phabricator.services.mozilla.com/D201385

UltraBlame original commit: ba8d0b7f1a2a1f0ae7d2dc42a2556789a6ab8ea2
gecko-dev-updater pushed a commit to marco-c/gecko-dev-comments-removed that referenced this issue Feb 20, 2024
@marco-c
Bug 1865837 - Add fetchpriority test for SVG <image> element. r=valen…
ec6ce44 
…tin,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 the `fetchpriority`
attributes (see w3c/svgwg#925) so the internal
priority should remain the same when the flag is enabled.

Differential Revision: https://phabricator.services.mozilla.com/D201385

UltraBlame original commit: ba8d0b7f1a2a1f0ae7d2dc42a2556789a6ab8ea2
jamienicol pushed a commit to jamienicol/gecko that referenced this issue Feb 20, 2024
@fred-wang
Bug 1865837 - Add fetchpriority test for SVG <image> element. r=valen…
c69460e 
…tin,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 the `fetchpriority`
attributes (see w3c/svgwg#925) so the internal
priority should remain the same when the flag is enabled.

Differential Revision: https://phabricator.services.mozilla.com/D201385
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@foolip @mbrodesser-Igalia