Bug 1516842

Summary: action bar kebab menu is cropped when the menu is long
Product: [oVirt] ovirt-engine Reporter: jniederm
Component: Frontend.WebAdminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: high    
Version: futureCC: bugs, gshereme, lleistne, oourfali
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:12:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vm-tiple-dot-menu.gif none

Description jniederm 2017-11-23 12:35:41 UTC
Created attachment 1358180 [details]
vm-tiple-dot-menu.gif

Description of problem:
See screenshot. Triple dot menu seems to be rendered inside of pane of VM details. Last item "Guide Me" is partially overlapped.

Version-Release number of selected component (if applicable):
current master, commit f7db909e5ba5723fe32ff1936835d029509257bd

How reproducible:
100%

Steps to Reproduce:
1. Open VM detail
2. Click triple dot toolbar button to open menu
3.

Actual results:
menu partially overlapped, looking like being inside the "Genaral" tab pane

Expected results:
menu rendered on top of the rest of the page

Additional info:

Comment 1 Oved Ourfali 2017-11-26 06:51:30 UTC
Alexander - is that a general issue, or specific to the VM's tab?

Comment 2 Greg Sheremeta 2017-11-29 12:15:11 UTC
It was a generic issue on every view

Comment 3 Lucie Leistnerova 2017-12-08 13:31:25 UTC
Triple dot menu all visible

verified in ovirt-engine-webadmin-portal-4.2.0-0.6.el7.noarch

Comment 4 Sandro Bonazzola 2017-12-20 11:12:55 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.