Created attachment 162880 [details] A DOCX with black text background Open the document. Select the whole table with black background; set font color Auto, and highlight color Auto (using toolbar buttons). Save as DOCX. Reload - the background is black again (and font color is black, too). Tested with Version: 7.0.0.1 (x64) Build ID: 04ba7e3f1e51af6c5d653e543a620e36719083fd CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: de-DE (ru_RU); UI: en-US Calc: CL
Reproduced in Version: 7.1.0.0.alpha0+ Build ID: 12bfedfac3b141fe6c91b0e5ae5b3fb2ba817c48 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded and Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.19; Render: default; Locale: en-US (en_US.UTF-8)
Created attachment 167754 [details] The example file in Writer 7.2master The black highlight comes from the paragraph style "Обычный".
Created attachment 167756 [details] In 6.0 and 6.1 Side note: the font color was black in 6.0 but since 6.1 it is white. Worth another report.
This should be fixed in 7.2 master courtesy of bug 137683 and others. https://cgit.freedesktop.org/libreoffice/core/log/?qt=grep&q=Char+highlight%3A The big problem with this particular document and the steps specified is that COL_AUTO was not being exported or imported.
(In reply to NISZ LibreOffice Team from comment #3) > Side note: the font color was black in 6.0 but since 6.1 it is white. Worth > another report. I'm not sure this is worth a report. Highlighting is a strange beast in Microsoft world, and we don't need to dirty our feet in every little fiasco related to it. COL_AUTO is doing what NORMALLY ought to be done - if the background is very dark, then the text will become light, and vice versa. So personally I would just leave this one alone.
Oh joy - now if you ONLY clear the highlight, it becomes white one white. But that is an older problem. On export, the character style changes w:color from auto to FFFFFF - so that's why, since font colour is no longer auto.
Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
IDK why this stayed open. Original issue is fixed.