Bug 155245 - LibreOffice Themes do not cover the entire toolbar on a high-DPI display (Windows)
Summary: LibreOffice Themes do not cover the entire toolbar on a high-DPI display (Win...
Status: RESOLVED DUPLICATE of bug 131023
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.7.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-11 15:24 UTC by kickers.stewed0j
Modified: 2023-05-11 16:01 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kickers.stewed0j 2023-05-11 15:24:19 UTC
Description:
Test case, LibreOffice on Windows.  Version 7.4.7.  The system has a 4K display running at 200% DPI scaling.  If a LibreOffice theme is set, it does not cover the entire width of the application window.

This is because the theme image files (i.e. share\gallery\personas\dark\header.png) are only 3000 pixels wide.  It is now common to have screens that are wider than that.

Easy fix: Make the theme image wide enough for today's displays.
Better fix: Have the taskbar tile the theme image horizontally?

Steps to Reproduce:
1. Run on a display more than 3000 pixels wide.  (A standard 4K display is fine.)
2. In LibreOffice options, under LibreOffice->Personalization, set a theme.
3. Now, open up LibreOffice Calc and maximize the window.

Actual Results:
The theme does not cover up the left side of the toolbar at the top.

Expected Results:
The theme should cover the entire top toolbar.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.4.7.2 (x64) / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 16; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 1 Stéphane Guillou (stragu) 2023-05-11 16:01:18 UTC

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