Bug 152946 - when sidebar is wider that some value, most of the final row of widgets is lost below the sidebar border, and is unreadable (but not necessarily unusable)
Summary: when sidebar is wider that some value, most of the final row of widgets is lo...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-09 12:49 UTC by xaxazak
Modified: 2023-10-21 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of issue (19.49 KB, image/jpeg)
2023-01-09 12:49 UTC, xaxazak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description xaxazak 2023-01-09 12:49:24 UTC
Created attachment 184543 [details]
Screenshot of issue

This might be DE-specific.
I'm using XFCE on Arch Linux.

This occurs regardless of whether the sidebar is docked.
This occurs on sidebars: [Styles], [Gallery], [Navigator], [Manage Changes]. (maybe others)
This only occurs if the sidebar is beyond a certain width. On [Styles], this is when the vertical scrollbar is fully visible. Shrinking the sidebar width fixes it, and widening it brings the bug back. (Note, this vertical scrollbar has no effect on this bug).

Could this be caused by something like reserving vertical space for a nonexistent horizontal scrollbar, causing a miscalculation in the sidebar height when positioning widgets.
Comment 1 Dieter 2023-02-01 07:10:38 UTC
I can't confirm with

Version: 7.5.0.2 (X86_64) / LibreOffice Community
Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

but I'm also not sure, if I've grasped the steps to reproduce. Perhaps it is possible for you to add a screencast? Might also be relevant to know the size and resolution of your display.
Comment 2 Buovjaga 2023-03-23 08:09:45 UTC
(In reply to Dieter from comment #1)
> I can't confirm with
> 
> Version: 7.5.0.2 (X86_64) / LibreOffice Community
> Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58
> CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL:
> win
> Locale: de-DE (de_DE); UI: en-GB
> Calc: CL threaded
> 
> but I'm also not sure, if I've grasped the steps to reproduce. Perhaps it is
> possible for you to add a screencast? Might also be relevant to know the
> size and resolution of your display.

I can't repro either. A screencast would be great.

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 6dfa9c7c0db91a71f3787226636864161d5367ca
CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 23 March 2023
Comment 3 QA Administrators 2023-09-20 03:06:33 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-10-21 03:15:42 UTC
Dear xaxazak,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp