Allow user to choose monitor profile and rendering intent
Reported by
enterthe...@gmail.com,
Jan 8 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Steps to reproduce the problem: A color-managed program should allow the user to specify a custom monitor profile and rendering intent. What is the expected behavior? What went wrong? Chromium does not let the user choose a custom monitor profile or rendering intent. It should let the user do that, without the requirement of the user installing a color-management service such as colord or oyranos, which have a poor track record of working correctly. Correctly color-managed programs such as RawTherapee and Geeqie let the user do just that. https://ninedegreesbelow.com/photography/monitor-profile-calibrate-confuse.html#choice Did this work before? N/A Chrome version: 63.0.3239.108 Channel: n/a OS Version: Flash Version:
,
Jan 9 2018
Ad.: 1. It's nice that Chromium detects the monitor from the X11 atom, but it should let the user specify a custom ICC profile. 2. It should let the user choose which rendering intent to use. 3. It should let the user choose whether to use black point compensation or not.
,
Jan 9 2018
s/the monitor/the monitor profile/
,
Jan 9 2018
,
Jan 10 2018
,
Jan 18 2018
I think we can add unofficial support for this via a command line argument (to a hardcoded path) -- adding UI or about:flags is unlikely (since IIUC we try to keep that to a minimum).
,
Jan 19 2018
Anything is better than nothing, though the unofficial support you're proposing would be a bizarre way of going about it considering Chromium already has (some, but not enough) color management settings in about:flags and considering color management is not territory of fringe maniacs but ordinary photographers, painters, artists and other arguably normal people. General remark, I wonder why so many programs treat people who invest time and money in correct color like third class citizens...
,
Yesterday
(46 hours ago)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Yesterday
(44 hours ago)
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Jan 9 2018Labels: Needs-Triage-M63 Triaged-ET M-65
Status: Untriaged (was: Unconfirmed)