Bug 139732 - UI: borders of slides not visable - no contrast with background
Summary: UI: borders of slides not visable - no contrast with background
Status: RESOLVED DUPLICATE of bug 134423
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-18 08:54 UTC by pieter kristensen
Modified: 2022-02-16 14:05 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
screen shot of the situation (153.74 KB, image/jpeg)
2021-01-18 08:54 UTC, pieter kristensen 		Details
plasma color scheme (2.66 KB, text/plain)
2021-01-18 08:54 UTC, pieter kristensen 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pieter kristensen 2021-01-18 08:54:16 UTC 
Created attachment 168979 [details]
screen shot of the situation

I am using LibreOffice on my KDE Neon machine. In Impress the left column of the UI uses the colors of the system in a rather strange way.
I attached a screen shot and the plasma color scheme I use.
In my opinion the contrast between the white of the "paper" and the background color should never be so small. 
I am aware that this might not be the most important bug. But just to let you know. 
In my opinion the work on LO in Plasma is really impressive! The program looks beautiful!
Comment 1 pieter kristensen 2021-01-18 08:54:53 UTC 
Created attachment 168980 [details]
plasma color scheme
Comment 2 pieter kristensen 2021-02-02 05:05:17 UTC 
When you look at the screenshot attached, take a look at the left vertical panel/pane of the Impress GUI (the one with the slides in it).
The color of the "paper" behind the slides (white) is almost the same as the background LibreOffice puts as background in this panel/pane.
This looks strange.
Comment 3 Buovjaga 2022-02-16 14:05:57 UTC 

*** This bug has been marked as a duplicate of bug 134423 ***