Bug 1461565 - Typeahead dropdowns seems to be rendered behind dialogs
Summary: Typeahead dropdowns seems to be rendered behind dialogs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Alexander Wels
QA Contact: samuel macko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-14 19:47 UTC by jniederm
Modified: 2017-12-22 07:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-12-20 11:05:00 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screenshot.png (45.61 KB, image/png)
2017-06-14 19:47 UTC, jniederm
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 78037 0 None None None 2017-06-21 14:33:57 UTC

Description jniederm 2017-06-14 19:47:50 UTC
Created attachment 1287771 [details]
screenshot.png

Description of problem:
When arrow down button of typeahead widget is clicked, the dropdown looks like rendered behind the dialog. Applies to Template and "nic1" fields in General tab of New VM dialog.

Version-Release number of selected component (if applicable):
current 4.2, commit 65646fc

How reproducible:
100%

Steps to Reproduce:
1. Open new VM dialog
2. Open dropdown "Template"
3.

Actual results:
See screenshot, dropdown looks like its under the dialog

Expected results:
dropdown rendered over the dialog

Additional info:

Comment 1 samuel macko 2017-09-04 13:43:50 UTC
Verified in ovirt version 4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos.

Verified by following the reproducer.

Comment 2 Sandro Bonazzola 2017-12-20 11:05:00 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.


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