Bug 1876820 - Need better alignment of menu items panels in libreoffice applications.
Summary: Need better alignment of menu items panels in libreoffice applications.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-08 09:17 UTC by Bhushan Barve
Modified: 2023-12-05 20:59 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-12-05 20:59:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Document Foundation 113713 0 None None None 2020-09-08 14:42:47 UTC
Red Hat Bugzilla 1380402 0 unspecified CLOSED Drop down menus that don't fit in available screen space cover menu bar before enabling scroll mode 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1646331 1 None None None 2021-02-20 06:20:58 UTC

Description Bhushan Barve 2020-09-08 09:17:34 UTC
Description of problem: The menu items panels for File and other menus in libreoffice applications need better alignment. For e.g. when clicked on file menu, the men items panel appears all over the window. Good to have it below the menu name. Refer attached screenshot.


Version-Release number of selected component (if applicable):
libreoffice-core-7.0.1.2-3.fc33.x86_64
F33 WS

How reproducible:
always

Steps to Reproduce:
1. Open any libreoffice application like oowriter
2. click on file menu at the top menu bar.
3. observe the menu item panel position

Actual results:


Expected results:
The menu item panel should be aligned properly, below the menu name.

Additional info:

Comment 1 Caolan McNamara 2020-09-08 14:42:48 UTC
There's no attachment but I imagine this is with the default gtk3 version and that the screen resolution is very low, like in the default configuration of a vm, and the native gtk menus overlap the native gtk menubar or something like that because it can't fit fully on screen in its preferred layout. If so, I imagine that the standalone reproducer of https://bugzilla.redhat.com/show_bug.cgi?id=1380402#c2 has the same sort of behavior and its not something LibreOffice has control over, but something belonging to the underlying gtk toolkit.

Comment 2 Ben Cotton 2021-11-04 17:32:46 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2022-11-29 16:49:28 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2023-11-23 00:03:39 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Aoife Moloney 2023-12-05 20:59:40 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.