Bug 1487193

Summary: [UI] add right margin to action buttons in detail view
Product: [oVirt] ovirt-engine Reporter: Lucie Leistnerova <lleistne>
Component: Frontend.WebAdminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, gshereme, pmatyas
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:24:07 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
action buttons none

Description Lucie Leistnerova 2017-08-31 12:19:00 UTC
Created attachment 1320567 [details]
action buttons

Description of problem:
When there are only few action buttons in detail view and no dropdown menu is shown, buttons are on the right border of the window.

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

How reproducible: always


Steps to Reproduce:
1. go to Network -> Networks
2. click on name of network to get detail view

Actual results: buttons are too much on the right, see attachment


Expected results: there is a space between right window border and buttons


Additional info:
The same is e.g in Administration -> Quota -> detail

Comment 1 Petr Matyáš 2017-09-07 10:05:04 UTC
Verified on ovirt-engine-webadmin-portal-4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos.noarch

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