Closed Bug 1860568 Opened 2 years ago Closed 2 years ago

Test the `fetchpriority` attribute is disabled when the corresponding pref is set to `false`

Categories

(Core :: Networking, defect, P2)

Product:
Core
Component:
Networking
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: mbrodesser, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

No description provided.
Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged]

Briefly discussed this with dholbert and jgraham.

There's no convenient way to achieve this and past experience showed that testing only one pref value is usually sufficient. An usual case might be a feature affecting many components, like Fission. That's not the case here.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.