Bug 51635

Summary: UI: The Menu Bar is not showing up correctly
Product: LibreOffice Reporter: Odomera <odomera>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: detective.conan.1412, LibreOffice
Priority: medium    
Version: 3.6.0.0.beta2   
Hardware: Other   
OS: Windows (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: Screenshot: Selected as the current window and deselect as current window
Menu bar in Windows 8 with different themes

Description Odomera 2012-07-01 16:47:52 UTC
Created attachment 63682 [details]
Screenshot: Selected as the current window and deselect as current window

Problem description: 
The menu bar is not displayed correctly using Windows 8 Release Preview 

Steps to reproduce:
1. Open LibreOffice Writer
2. See the Menu bar

Current behavior:
The commands (texts) in the Menu Bar is not displayed correctly. 

Expected behavior:
I should be able to read the menus texts

Platform (if different from the browser): 
Windows 8 Release Preview (32 bits) 
              
Browser: Mozilla/5.0 (Windows NT 6.2) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11
Comment 1 Rainer Bielefeld Retired 2012-07-01 21:18:58 UTC
"Not correctly" is very rare ...

@Odomera:
Your problem seems to be that in inactive Window contrast between characters and background in Menu bar is too small?
Comment 2 Odomera 2012-07-04 07:40:46 UTC
Created attachment 63809 [details]
Menu bar in Windows 8 with different themes

The font in the menu bar is transparent or translucent. When I change the theme in Windows (with or without Aero transparency) the font took the color of the title bar or shows transparent.
Comment 3 vitriol 2012-07-04 07:45:15 UTC
Maybe fixed in 3.6 Beta 3: Bug 50036
Comment 4 Korrawit Pruegsanusak 2012-07-17 14:15:17 UTC
No answer, so mark as duplicate.

Odomera, please feel free to reopen if your problem still occur with latest pre-release, or you think this bug is different. Thanks.

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