Bug 682033 - Switching from High Contrast to High/Inverse or Low Doesn't Do Anything
Summary: Switching from High Contrast to High/Inverse or Low Doesn't Do Anything
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-themes-standard
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cosimo Cecchi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-03 23:59 UTC by David Le Sage
Modified: 2011-04-07 23:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-07 23:44:47 UTC
Type: ---


Attachments (Terms of Use)

Description David Le Sage 2011-03-03 23:59:34 UTC
Description of problem:
If you switch the contrast setting from High to High/Inverse or Low, nothing happens.

Version-Release number of selected component (if applicable):
control-center-2.91.90-2.fc15.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Log into the GNOME Shell.
2. Click on User Name (top right-hand corner)
3. Choose System Settings from the drop-down menu.
4. Choose Universal Access from the list.
5. Under the "Seeing" tab, switch the contrast from Normal to High.  The colour scheme changes.
6. Now switch from High to High/Inverse.  Nothing happens.
7. Now switch from High to Low.  Nothing happens.
  
Actual results:
Doesn't change.

Expected results:
Colour theme should change.

Additional info:
Ironically, at the moment, "Normal" seems much higher contrast than high, due to the strong white background in these theme, whereas High has the softer grey theme.  I suspect the themes have actually been given the wrong names (sorry in advance if I am incorrect about this and they are right.)

Comment 1 Bastien Nocera 2011-03-04 15:12:28 UTC
Was bugs in gnome-themes-standard missing those variants.

Comment 2 Matthias Clasen 2011-04-07 23:44:47 UTC
Those variants are present now.


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