Bug 56814 - VIEWING: On Windows icons stay high contrast after switch to high contrast and back.
Summary: VIEWING: On Windows icons stay high contrast after switch to high contrast an...
Status: RESOLVED DUPLICATE of bug 41450
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.6.3.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-06 18:17 UTC by e325001
Modified: 2012-11-06 20:38 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Impress with high contrast icons while theme isn't high-contrast. (173.29 KB, image/png)
2012-11-06 18:17 UTC, e325001 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description e325001 2012-11-06 18:17:54 UTC 
Created attachment 69632 [details]
Impress with high contrast icons while theme isn't high-contrast.

Problem description:
After switching to high contrast Windows theme and back icons in LO stay high-contrast.

Steps to reproduce:
1. Open Impress/Writer/etc.
2. Switch Windows to high contrast theme.
3. Switch back to "normal" theme.
4. Icons in LO are still high contrast ones.

Current behavior:
After switching to high contrast Windows theme and back icons in Impress stayed high-contrast. While it was running every other copy of Impress or any other LO app had high contrast icons. After closing all LO apps icons are back to normal.

Expected behavior:
Icons in LO should switch back to normal when Windows theme is switched back to normal.

Platform (if different from the browser): 
Windows 8 Pro x64
              
Browser: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
Comment 1 bfoman (inactive) 2012-11-06 20:32:06 UTC 
Bug 43131 comment 1 describes similar behavior on Windows 7.
Comment 2 bfoman (inactive) 2012-11-06 20:38:00 UTC 
Do not hesitate to reopen in case of mistriage.

*** This bug has been marked as a duplicate of bug 41450 ***