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

            Bug ID: 166437
           Summary: Spell check dark mode causes automatic text to be
                    black
           Product: LibreOffice
           Version: 25.2.2.2 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Description:
When LibreOffice is in dark mode, and the language of the document is set to
something other than 'none' (English in my case), any word that is flagged by
spell check and has the red underline becomes black instead of staying white.
This makes it hard to read since the background is also black. The text is set
to automatic, not white or black, so it should stay consistent with the dark
mode setting. Changing the document language to 'none' fixes the issue since
spell check becomes disabled, so the red underline disappears and the text
becomes white again.

Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID:
7370d4be9e3cf6031a51beef54ff3bda878e3fac CPU threads: 4; OS: Windows 10 X86_64
(10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI:
en-US Calc: threaded 

Steps to Reproduce:
1.Set LibreOffice to dark mode.
2.Set the spreadsheet language to english (or something other than none).
3. Set the text color to automatic.
4. Enter a string that will be flagged by spell check.


Actual Results:
The text has a red underline and changes to black from white.

Expected Results:
The text has a red underline but stays white.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID:
7370d4be9e3cf6031a51beef54ff3bda878e3fac CPU threads: 4; OS: Windows 10 X86_64
(10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI:
en-US Calc: threaded

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

Reply via email to