Bug 118158 - in high contrast mode the preview of table borders shows no colors
Summary: in high contrast mode the preview of table borders shows no colors
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: High-Contrast
  Show dependency treegraph
Reported: 2018-06-14 09:50 UTC by Regina Henschel
Modified: 2019-06-26 02:46 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2018-06-14 09:50:46 UTC
Switch to a high-contrast theme of Windows. Start LibreOffice and insert a table. Open the properties dialog tab Borders. Select a border line in the preview on the left side of the dialog. Increase border width, so you can better see the border line in the preview. Change the color of the border line to something different from black. Notice that the color in the preview do not change. OK. Notice, that the color in the document has changed.

The problem is, that you only need the dialog, if you want some special border line settings, e.g. different colors for outer and inner lines. And exact that is not visible in high-contrast mode.
Comment 1 Regina Henschel 2018-06-14 10:09:55 UTC
The situation is worse for other objects, that use the same dialog. For example a frame does not show the applied color at all, but it has still the default black. But the color is set, which you will notice in the thumbnail and of cause is pdf export and print.
Comment 2 Buovjaga 2018-06-24 10:23:55 UTC

Merge adjacent line styles has to be unticked, if we modify a single line.

Version: (x64)
Build ID: 2c85607101e2e04e870e3b87362f39f9a9148e6c
CPU threads: 4; OS: Windows 10.0; UI render: default; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-06-16_00:12:37
Locale: fi-FI (fi_FI); Calc: group threaded
Comment 3 QA Administrators 2019-06-26 02:46:22 UTC
Dear Regina Henschel,

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team