1920222 - Consider modifying the fetchpriority adjustments for <img> elements so that priority="low" is given a lower priority than auto / no attribute

Status: RESOLVED FIXED

(Core :: Networking, task, P3)

Description

[Andrew Creskey [:acreskey]]

Our initial configuration for fetchPriority on <img> elements gives a priority boost when fetchprioty="high", but applying the fetchprioty="low" attribute does not modify priority:

- name: network.fetchpriority.adjustments.images.low
  type: int32_t
  value: 0
  mirror: always
- name: network.fetchpriority.adjustments.images.high
  type: int32_t
  value: -20
  mirror: always
- name: network.fetchpriority.adjustments.images.auto
  type: int32_t
  value: 0
  mirror: always

See prefs

Note that images in Firefox have a default priority of "low".

But one use case of fetchPriority is to de-prioritize low value images (by tagging as "low" priority).

Attaching a patch for discussion in which network.fetchpriority.adjustments.images.low reduces priority one increment.

Comment 1

[Andrew Creskey [:acreskey]]

Attachment: Bug 1920222 - Modify the fetchpriority adjustments for <img> elements so that priority="low" is given a lower priority than auto / no attribute r=#necko-reviewers

Set adjustment for fetchpriority="low" on images to deprioritize so developers can reduce bandwidth shared to tagged images.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/842e525e2dd7
Modify the fetchpriority adjustments for <img> elements so that priority="low" is given a lower priority than auto / no attribute r=necko-reviewers,fredw,kershaw

Comment 3

[Cristina Horotan [:chorotan]]

https://hg.mozilla.org/mozilla-central/rev/842e525e2dd7