Bug #94713 MacOS Dark mode value editor has illegible text due to colour
Submitted: 20 Mar 2019 8:20 Modified: 23 Mar 2019 5:34
Reporter: Ferdi S Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:8.0.15, 8.0.18, 8.0.31, 8.0.36 OS:MacOS
Assigned to: CPU Architecture:x86

[20 Mar 2019 8:20] Ferdi S
Description:
The value editor for columns when using dark mode on MacOS has no contrast difference to differentiate the text from the background, making it incredibly hard to read.

How to repeat:
1. Right-click a column with a value
2. Select "Edit Value in Editor"
3. Select the "Text" or "JSON" tab

Suggested fix:
Whiten the text in dark mode to make it leggible.
[20 Mar 2019 8:21] Ferdi S
When the editor is inactive

Attachment: Screenshot 2019-03-20 at 10.17.35.png (image/png, text), 95.50 KiB.

[20 Mar 2019 8:21] Ferdi S
When the editor is active

Attachment: Screenshot 2019-03-20 at 10.17.37.png (image/png, text), 95.78 KiB.

[22 Mar 2019 13:27] Neo Ramos
The text on the left panel where Management, Instance, performance and schema options are displayed does not display correctly.  The font appears smeared and there is black font on a dark grade which is hard to read. 

In addition:
- When altering a table, the apply / revert buttons are white font on very light gray (hard to read)
- Other parts of the lower part of screen the text is invisible
[22 Mar 2019 13:27] Neo Ramos
Sample Mysql workbench 8 screenshot with color issues

Attachment: MySQL_Workbench_8_Color_issues.jpg (image/jpeg, text), 306.62 KiB.

[23 Mar 2019 5:34] MySQL Verification Team
Hello Ferdi S,

Thank you for the report and feedback.
Verified as described with MySQL Workbench Community (GPL) for Mac OS X version 8.0.15 CE build 14271522 (64 bit) on macOS 10.14.x Mojave x86_64 with dark mode enabled.

regards,
Umesh
[6 Nov 2019 11:31] MySQL Verification Team
Bug #97505 marked as duplicate of this one
[16 Nov 2022 12:18] MySQL Verification Team
Bug #109090 marked as duplicate of this one
[24 Jun 2024 13:18] MySQL Verification Team
Bug #115404 marked as duplicate of this one