Bug 1511906 - on screen resolution 1368x768 is host dialog header not visible
Summary: on screen resolution 1368x768 is host dialog header not visible
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Greg Sheremeta
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks: 871420
TreeView+ depends on / blocked
 
Reported: 2017-11-10 12:00 UTC by Lucie Leistnerova
Modified: 2017-12-20 11:37 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
host new dialog (64.59 KB, image/png)
2017-11-10 12:00 UTC, Lucie Leistnerova 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84010 0 None None None 2017-11-30 16:22:21 UTC

Description Lucie Leistnerova 2017-11-10 12:00:48 UTC 
Created attachment 1350438 [details]
host new dialog

Description of problem:
Header of new/edit host dialog is not visible in resolution 1368x768.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.2.0-0.0.master.20171108151837.gita7de53e.el7.centos.noarch

How reproducible: always


Steps to Reproduce:
1. go to Hosts
2. click on New
3.

Actual results: header not visible, see attachment


Expected results: header visible, end of dialog scrollable
Comment 1 Lucie Leistnerova 2017-12-07 12:47:05 UTC 
Whole dialog visible/scrollable

verified in ovirt-engine-webadmin-portal-4.2.0-0.6.el7.noarch
Comment 2 Sandro Bonazzola 2017-12-20 11:37:29 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.