Bug 97136 - Scrolled menu items don't respond to mouse events
Summary: Scrolled menu items don't respond to mouse events
Status: RESOLVED DUPLICATE of bug 92702
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
5.0.3.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-14 13:59 UTC by Laurentiu Pancescu
Modified: 2016-01-14 17:57 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
The File/Quit menu item not being highlighted (70.33 KB, image/png)
2016-01-14 13:59 UTC, Laurentiu Pancescu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Laurentiu Pancescu 2016-01-14 13:59:41 UTC
Created attachment 121933 [details]
The File/Quit menu item not being highlighted

When a menu is taller than the screen height, it is clipped, with arrows on top and bottom for scrolling.  However, the newly scrolled menu items don't highlight when the mouse cursor is moving over them, and clicking on e.g. "Quit" from the "File" menu has no effect.  The menu items which were already visible when the menu opened DO respond to mouse movement and clicking; only the previously hidden menu items have this issue.  This happens with LibreOffice 5.0.3 from Fedora 23; version 4.4.7 from Fedora 22 works as expected.

Workaround: use the up/down arrow keys to navigate in the menu, once opened.  The menu items are highlighted correctly, and pressing Enter activates the menu, triggering the expected action.

I attached a screenshot taken on a netbook running the Fedora 23 XFCE Spin, showing the File/Quit menu item not responding.  I have the same problem with any menu needing scrolling, not just in Calc but also in Writer (didn't try Impress).  In the screenshot, the last 3 menu items were initially not visible, and don't react to mouse events.
Comment 1 Maxim Monastirsky 2016-01-14 17:57:58 UTC
Thanks for reporting. Should be fixed as of 5.0.4.

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