Open
Bug 1375181
Opened 8 years ago
Updated 3 years ago
color management destaturated image
Categories
(Core :: Graphics: Color Management, defect, P3)
Tracking
()
UNCONFIRMED
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: mati.798, Unassigned)
Details
(Keywords: regressionwindow-wanted, Whiteboard: [gfx-noted])
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170608105825
Steps to reproduce:
I have a monitor with wide color gamut (calibrated) and installed ICC v.2 profile in Windows 10.
I prepared one image without included ICC profile and EXIF tags inside (checked by exiftool)
Settings:
gfx.color_management.mode = 1
I have found some webpages where I could upload images through browser (e.g. olx) and did it.
Actual results:
When you finally uploaded image to the website you can see that the image is desaturated compare to original jpg. It looks like it has been converted to monitor profile twice.
I mean when you have gfx.color_management.mode = 2 that everything is oversaturated (page elements) and on value 1 is ok but each uploaded image is desaturated.
If you use Chrome or another browser (even Safari on Mac) to upload this photo and see the results on Firefox that everything looks great (I want to point out that I'm using the same image!)
Unfortunately it is not the calibration fault and Windows too.
Furthermore Firefox Developer Edition has the same issue when gfx.color_management.mode is set to 1.
Expected results:
The images shouldn't be desaturated because the result of Firefox behaviour is visible for all browsers after all.
I guess Firefox processes images on the fly incorrectly.
Updated•8 years ago
|
Component: Untriaged → ImageLib
Product: Firefox → Core
I'm assuming this is not a recent regression - did this ever work in Firefox? mozregression tool can tell us.
status-firefox57:
--- → wontfix
Component: ImageLib → GFX: Color Management
Keywords: regressionwindow-wanted
Priority: -- → P3
Whiteboard: [gfx-noted]
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•