Bug 843764 - 'High Contrast' accessibility option doesn't activate in the login screen (gdm frontend)
'High Contrast' accessibility option doesn't activate in the login screen (gd...
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: beta
: ---
Assigned To: Florian Müllner
Desktop QE
Depends On:
  Show dependency treegraph
Reported: 2012-07-27 05:51 EDT by Vitezslav Humpa
Modified: 2012-10-18 12:41 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-10-17 17:32:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vitezslav Humpa 2012-07-27 05:51:37 EDT
Description of problem:
Using the accessibility menu of the same kind as inside the logged gnome-session, the 'High Contrast' option doesn't make any changes to the theme in the login screen (gnome-shell front-end for gdm).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Toggle 'High Contrast' on in the login screen
Actual results:
Nothing happens

Expected results:
Theme switches to high contrast
Comment 1 Matthias Clasen 2012-10-17 17:32:11 EDT
I don't think this is a bug, really. It is just that the shell itself does not have any highcontrast theme - if you go to an empty desktop while logged in, and hit the highcontrast switch, you won't see any difference either.
Comment 2 Florian Müllner 2012-10-17 17:45:48 EDT
Maybe it makes sense to hide the High Contrast switch on the login screen? I can see how it is confusing ...
Comment 3 Matthias Clasen 2012-10-18 12:38:50 EDT
Lets take this to an upstream bug where I can just add the 'ui-review' keyword
Comment 4 Matthias Clasen 2012-10-18 12:41:29 EDT

Note You need to log in before you can comment on or make changes to this bug.