Description: The user cannot see the text because it is black against a black background. Notably, if Font Color is set to white, the issue persists. Steps to Reproduce: 1. Open LibreOffice. Go to Tools -> Options -> LibreOffice -> Application Colors -> Document Background -> Color setting = Black. 2. Close the Options dialogue, and the foreground text should have become white, automatically, conveniently. 3. Restart the application and open the same document, and the text will now be black. Go back to Application Colors and set the Font Color to White: the problem will persist, and the font will remain black. Actual Results: The foreground and background are both black. Expected Results: The foreground text should be white, and the document background should be black. A normal inverted-color setting. Reproducible: Sometimes User Profile Reset: No Additional Info: Workaround: Every time the document is opened, you can select all of the text and set the Font Color to Automatic in the toolbar; however, this is not ideal. In fields where documents use a lot of colorized text, using this workaround will cause too many problems, and it is better to use a white document background. It's very good for reducing eye strain and minimizing interference with circadian rhythms to solve this bug. Because it's good for human health, I hope that the bug is prioritized. Thank you. User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
I can not confirm with 5.4.1.2, windows and Version: 6.0.0.0.alpha0+ Build ID: afeff9102c2935139de4efd40fd2286dce396706 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-09-17_23:32:41 Font color: automatic Please install newer version and retest. If bug still persist, set bug status as unconfirmed. Closing as WFM. http://www.libreoffice.org/download/
*** Bug 114084 has been marked as a duplicate of this bug. ***
Testing 5.4.3.2 and 6.1.0 master with STR from dupe bug 114084... confirming mishandling with Windows 10 Home 64-bit en-US (ver 1709) in HighContrast modes (HC black, HC white, or HC #1, HC #2). However, when I set Tools -> Options -> Accessibility -> Options for High Contrast Appearance: "Automatically detect high contrast mode of operating system" AND/OR "Use automatic font color for screen display"--on restarting LibreOffice I get reasonable font color and background colors as defined in any of the HC themes. But some of the "automatic" colors do not render GUI components well--the HC #2 theme is probably the most readable. So, setting the LO Accessibility HC options is needed (no it should not be enabled by default) and this issue is not valid. But we may need to tweak the automatic colors being picked up from the theme to be sure all our GUI controls show, i.e. the main menu. And, the HC icon set still needs work. Likely using Sifr as for bug 75398 STR from bug 114084 <clip> Description: Opening a .docx file results in black text and a black background. Steps to Reproduce: Make sure LibreOffice's document color background is set to black by pressing Alt-F12, selecting `Application Colors` and setting the background color to black. This bug was cancelled by someone, but it actually is not resolved. In Windows 10, put the computer into high contrast mode by pressing `Alt-Shift-PrtSc`. Now, open a .docx (MS Word 2007-2013 XML) file. *Notably: this error persists even if the text color is set to white. Actual Results: If the file has any normal/black text, the text will all be black against the black background so you won't be able to see any of it. Expected Results: The text should be white because selecting all of the text and clicking `Text Color -> Automatic` results in white text; furthermore, user sets the text color to white in the settings. </clip>
Resolving this and dupe bug 114084 as NOTABUG as correct automatic font color selection when OS is in a High Contrast theme simply requires setting the correct LO mode from Tools -> Options -> Accessibility settings.
*** Bug 109121 has been marked as a duplicate of this bug. ***