Bug #72372 | Workbench colour scheme is inconsistent and difficult/impossible to configure | ||
---|---|---|---|
Submitted: | 17 Apr 2014 17:32 | Modified: | 18 Apr 2014 10:26 |
Reporter: | Alain Forget | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.1.4.11773, 6.3.10 | OS: | Windows (8.1) |
Assigned to: | CPU Architecture: | Any | |
Tags: | accessibility, color, high contrast, scheme, theme, user interface, visual |
[17 Apr 2014 17:32]
Alain Forget
[17 Apr 2014 17:33]
Alain Forget
Screenshot of MySQL Workbench 6.1.4 with the Windows 8.1 High Contrast Black theme. Only Schema, Output, and tabs appear correct
Attachment: HighContrastBlack.png (image/png, text), 57.43 KiB.
[17 Apr 2014 18:25]
Alain Forget
The Preferences dialog appears to render correctly, using the Windows theme defaults, as does Schema sub-box, Output sub-box, and tabs.
[17 Apr 2014 21:48]
MySQL Verification Team
According your last comment the issue was fixed?. Thanks.
[17 Apr 2014 21:56]
Alain Forget
No, not at all. The rest of the user interface is black text on white background, rather than the expected other way around. I was just pointing out that the Preferences dialog box does display correctly, so developers could also use it to see how the colouring can be done correctly, like in the Schema sub-box, Output sub-box, and the tabs.
[18 Apr 2014 10:26]
MySQL Verification Team
Hello Alain, Thank you for the feedback. Verified as described on Win7 with WB 6.1.4 Thanks, Umesh
[12 Jun 2017 13:14]
Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=86644 marked as duplicate of this one.
[24 Jul 2017 10:12]
Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=87168 marked as duplicate of this one.
[16 Mar 2018 10:04]
Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=89827 marked as duplicate of this one.
[16 Mar 2018 10:16]
Luki BS
So it's not verified for Windows 10 with High Contrast Theme yet. My previous report is on #89827 and marked as duplicate.
[6 Jun 2018 6:03]
MySQL Verification Team
Bug #90721 marked as duplicate of this one
[8 Mar 2022 14:49]
MySQL Verification Team
Bug #106649 marked as duplicate of this one