New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 718400 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ shrike@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

[mac] Display::is_mononchrome not updated when monochrome enabled through accessibility

Project Member Reported by ccameron@chromium.org, May 4 2017 
We set Display::set_monochrome based on CGDisplayUsesForceToGray in BuildDisplayForScreen(NSScreen*).

We then re-compute the value based on CGDisplayRegisterReconfigurationCallback.

The value of CGDisplayUsesForceToGray changes when the screen is forced to grayscale in System Preferences->Accessibility.

We do not trigger the DisplayReconfigurationCallBack function, and so we are left with the old value. We should make this callback when the value of CGDisplayUsesForceToGray will change.

Comment 1 by ccameron@chromium.org, May 4 2017 

Note that when we do trigger DisplayReconfigurationCallBack (e.g, but changing the desktop resolution), we pick up the new value from CGDisplayUsesForceToGray.
Project Member

Comment 2 by sheriffbot@chromium.org, May 4 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Comment 3 by lgrey@chromium.org, May 7 2018 

ccameron@ is this still relevant?

Comment 4 by ccameron@chromium.org, May 15 2018 

It's still true, but there are many more important things to work on.

Comment 5 by erikc...@chromium.org, May 16 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment