Closed
Bug 1294948
Opened 8 years ago
Closed 8 years ago
Firefox and color management
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: veranyon, Unassigned, NeedInfo)
Details
(Whiteboard: [gfx-noted])
Attachments
(1 file)
2.03 MB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7 Steps to reproduce: Open any site, where are graphic elements. Any site. Actual results: Oversaturated colors on any site. I don't know when it's beginned. Only know that ff hadn't that problem early. Expected results: I test to change firefox' settings (http://ntown.at/2013/12/28/firefox-color-management/) but that changes can't helped. My OS: OS X EL Capitan 10.11.6 FF v: 48.0. I attach an example of that issue.
Reporter | ||
Updated•8 years ago
|
Component: Graphics → General
OS: Unspecified → Mac OS X
Product: Core → Firefox
Hardware: Unspecified → x86_64
Comment 1•8 years ago
|
||
Thanks for the report! Can you try to use mozregression ( http://mozilla.github.io/mozregression/ ) to figure out when this problem started for you? Milan, any chance this is caused by the switch to... whatever it was we switched to on OSX? I don't remember right now...
Component: General → Graphics
Flags: needinfo?(veranyon)
Flags: needinfo?(milan)
Product: Firefox → Core
Reporter | ||
Comment 2•8 years ago
|
||
I can't to understood how use that mozregression. That one use a some "academically" style. Not for a simple user. Thank you. Perhaps left to safari web browser, again.
Just to be clear: gfx.color* preferences are at their default value when this happens? What happens if you change gfx.color_management.mode to 0 instead of the default 2 (and restart)?
Flags: needinfo?(milan)
Whiteboard: [gfx-noted]
Reporter | ||
Comment 4•8 years ago
|
||
The problem was been resolved. My mistake that I set icc file path incorrectly.
Reporter | ||
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•