https://bugs.documentfoundation.org/show_bug.cgi?id=149606

            Bug ID: 149606
           Summary: "Set Paragraph Style" Options are Unreadable in Dark
                    Mode
           Product: LibreOffice
           Version: 7.3.3.2 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: UI
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: christian.hollinger2...@gmail.com

Description:
I am using the openSUSE Dark system theme, Breeze (dark) Icon style,
LibreOffice Dark color scheme, and default ("do not use Themes") LibreOffice
theme. I have changed no other values.

The options in the "Set Paragraph Style" selector (both the combo box at the
top-left and the "Styles" tool in the right sidebar) have black text and cannot
be seen against the dark background. For the combo box in the top-left, the
only way to see the options is to hover the mouse over them, which turns the
background white. For the "Styles" tool in the sidebar, I have to click on a
Style to lighten the background in order to actually read the foreground text
(style title). I tried messing around with various settings but nothing seems
to be working.

This only seems to affect Write.

Steps to Reproduce:
1. Set visual options as described in the first paragraph of this bug's
Description.
2. Either click on the "Set Paragraph Style" selector at the top left to open
the options, or open the "Styles" tool in the sidebar.

Actual Results:
Options are unreadable.

Expected Results:
Used light colors for the foreground text, or a lightly colored background.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.3.3.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 6; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to