Bug 137956 - Draw a bevel around previews
Summary: Draw a bevel around previews
Status: RESOLVED DUPLICATE of bug 138010
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks:
 
Reported: 2020-11-03 10:12 UTC by Heiko Tietze
Modified: 2020-11-10 12:42 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example (23.71 KB, image/png)
2020-11-03 10:12 UTC, Heiko Tietze
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Tietze 2020-11-03 10:12:36 UTC
Created attachment 166966 [details]
Example

Previews are flat images today looking unattached. While flat is modern in mobile UIs the good old bevel gives also a clue that this element offers no interaction.

The example shows the current flat character style preview while above with a bevel using the Shadow and DarkShow colors of the Breeze color theme. In would be inverted in case of Breeze Dark and the upper border becomes light grey while the lower is white then.
Comment 1 Michael Weghorn 2020-11-06 14:04:44 UTC
Is this only with the kf5 VCL plugin?

At a quick glance, it looks like the underlying cause may be the same as underlying bug 138010 which you've added as "See also". As described in bug 138010 comment 2, I also see borders for the character dialog when using either the Fusion theme or the demo patch at https://gerrit.libreoffice.org/c/core/+/105408 (but I'm not so sure whether this is the right way to go...).

This may need further investigation, and maybe discussion with the Breeze theme authors.
Comment 2 Heiko Tietze 2020-11-06 14:06:18 UTC
My "demo" patch https://gerrit.libreoffice.org/c/core/+/105237
Comment 3 Heiko Tietze 2020-11-10 12:42:46 UTC
Scrollwindow should have a border, and does with gen and gtk3. But not kf5, so this is a bug and has been reported.

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