You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All text should be easily readable when in dark mode.
For example, under 5.2.7:
Current Behavior
Comments in the pipeline rule "source code editor" are difficult to read when dark mode is used.
Under 6.0.1 (with the same text):
Steps to Reproduce (for bugs)
Be on at least 6.0.0 and use dark mode
Open the pipeline rule source code editor and add a rule with some comments
Note it's somewhat difficult to read the comment text (slightly better when the row is selected)
Context
Not being able to clearly read all text makes working with pipeline rules more difficult under 6.0.x.
Somewhat related: the table header background color is also not great in dark mode under 6.0.x (message tables, Users list, Event Definitions list, etc.). It'd be nice if there was more contrast.
Your Environment
Graylog Version: 6.0.1
Browser version: Firefox 125, Chrome 124
The text was updated successfully, but these errors were encountered:
coffee-squirrel
changed the title
Comments difficult to read in pipeline rule "source code editor" when dark mode is used
Comments difficult to read in pipeline rule "source code editor" when dark mode is used (6.x)
May 15, 2024
Expected Behavior
All text should be easily readable when in dark mode.
For example, under
5.2.7
:Current Behavior
Comments in the pipeline rule "source code editor" are difficult to read when dark mode is used.
Under
6.0.1
(with the same text):Steps to Reproduce (for bugs)
6.0.0
and use dark modeContext
Not being able to clearly read all text makes working with pipeline rules more difficult under
6.0.x
.Somewhat related: the table header background color is also not great in dark mode under
6.0.x
(message tables, Users list, Event Definitions list, etc.). It'd be nice if there was more contrast.Your Environment
6.0.1
125
, Chrome124
The text was updated successfully, but these errors were encountered: