Bug 1572157

Summary: bad checkbox spacing in Logical Networks > New > Cluster
Product: [oVirt] ovirt-engine Reporter: Krishna Babu K <kkrothap>
Component: Frontend.WebAdminAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Roni <reliezer>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0CC: bbarve, bugs, danken, kkrothap, reliezer, ylavi
Target Milestone: ovirt-4.2.4Flags: rule-engine: ovirt-4.2+
ylavi: exception+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-26 08:40:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen-shot reference for reported issue none

Description Krishna Babu K 2018-04-26 09:46:17 UTC 
Description of problem:

Layout is inconsistent in Firefox. The checkbox is slightly overlapping the text.


Version-Release number of selected component (if applicable):
RHV 4.2

How reproducible:
alsways

Steps to Reproduce:
1. Go to Welcome page > Administration Portal and login with Admin credentials 
2. Go to Data Centers tab 
3. Click on Logical Network > New > Cluster

Layout is inconsistent in Firefox. The checkbox is slightly overlapping the text.


Actual results:
Layout is inconsistent in Firefox. The checkbox is slightly overlapping the text.


Expected results:
should not overlap

Additional info:
Comment 1 Krishna Babu K 2018-04-26 10:00:38 UTC 
Created attachment 1427119 [details]
screen-shot reference for reported issue
Comment 2 Roni 2018-05-27 13:27:06 UTC 
verified on 4.2.4-0.1.el7
Comment 3 Sandro Bonazzola 2018-06-26 08:40:14 UTC 
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE.

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