Add a pref for the Accept header for images

RESOLVED WONTFIX

Status

()

enhancement
RESOLVED WONTFIX
12 years ago
9 years ago

People

(Reporter: glandium, Unassigned)

Tracking

unspecified
Points:
---
Dependency tree / graph
Bug Flags:
wanted1.9.2 ?

Firefox Tracking Flags

(blocking2.0 -)

Details

(Reporter)

Description

12 years ago
Please add a preference for the Accept request header for images, as set in imageLoader's NewImageChannel, to be customized, as it is currently possible for normal HTTP requests with network.http.accept_default.
(Reporter)

Updated

12 years ago
Blocks: mng

Comment 1

12 years ago
Should this be a single pref?  Or should it be something similar to general.useragent.extra.*, so each extension that adds to the Accept header can do so by having a default pref?
(Reporter)

Comment 2

12 years ago
That's indeed a good question. I have no strong opinion on that, but the same rationale could be applied to network.http.accept.default, too...

As for implementation details, do you think it would be best to query the prefservice each time or add a member to the class, set it to the value of the pref at instanciation time, and add an observer to modify its value when the pref change ?
Blocks: 88020
Flags: wanted1.9.2?

Updated

9 years ago
blocking2.0: --- → ?
We should totally take a patch - I might even write one - but this doesn't block the release.
blocking2.0: ? → -
Image decoders and User-Agent strings are no longer extensible. Is this bug still valid?
(In reply to comment #4)
> Image decoders and User-Agent strings are no longer extensible. Is this bug
> still valid?

I believe that it is not.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 6

9 years ago
For those like me who wondered why: https://bugzilla.mozilla.org/show_bug.cgi?id=513681#c7
You need to log in before you can comment on or make changes to this bug.