Bug 1450662 - [UI] - Gap between 'Virtual Size' and 'Attached To' separate line header under 'VMs' > 'Disks'
Summary: [UI] - Gap between 'Virtual Size' and 'Attached To' separate line header unde...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Greg Sheremeta
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-14 13:24 UTC by Michael Burman
Modified: 2017-12-22 07:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:36:21 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screenshot (82.06 KB, image/png)
2017-05-14 13:24 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 76097 0 None None None 2017-06-20 20:57:10 UTC

Description Michael Burman 2017-05-14 13:24:15 UTC
Created attachment 1278652 [details]
screenshot

Description of problem:
[UI] - Gap between 'Virtual Size' and 'Attached To' separate line header under 'VMs' > 'Disks'. 

There is a cosmetic gap in the separate line header Under 'VMs' main tab > 'Disks' sub tab.  

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170512134658.git7d2e44a.el7.centos

How reproducible:
100

Steps to Reproduce:
1. Go to 'VMs' main tab > 'Disks' sub tab 

Actual results:
A cosmetic gap between the 'Virtual Size' and 'Attached To' separate line header

Expected results:
No gaps in the separate line headers.

Comment 1 Oved Ourfali 2017-05-15 05:02:11 UTC
Sounds like a storage specific issue.
Allon/Tal - if I'm wrong, please move it back to UX.

Comment 2 Allon Mureinik 2017-05-15 10:34:59 UTC
(In reply to Oved Ourfali from comment #1)
> Sounds like a storage specific issue.
> Allon/Tal - if I'm wrong, please move it back to UX.

Seems so, thanks.

Comment 3 Lucie Leistnerova 2017-05-16 09:19:36 UTC
The same is here:
main Disk tab before Status and Type
Add users and groups before First Name
in config MAC Adress Pools and Scheduling Policies

Should I create another BZ, because it's not only in storages?

Comment 4 Michael Burman 2017-05-16 11:05:07 UTC
Maybe this is caused by the fix for BZ 1403847 ?

Comment 5 Oved Ourfali 2017-05-16 11:11:38 UTC
(In reply to Lucie Leistnerova from comment #3)
> The same is here:
> main Disk tab before Status and Type
> Add users and groups before First Name
> in config MAC Adress Pools and Scheduling Policies
> 
> Should I create another BZ, because it's not only in storages?

I'd imagine different bug per vertical.
But, let's first see what Vojtech things about what Michael asked.

Comment 6 Greg Sheremeta 2017-05-22 16:36:14 UTC
It's caused by there being several 1px wide "hidden" columns there.

This is fixed in my grid update patch, https://gerrit.ovirt.org/#/c/71545/

Comment 7 Vojtech Szocs 2017-05-31 16:09:54 UTC
(In reply to Michael Burman from comment #4)
> Maybe this is caused by the fix for BZ 1403847 ?

Sorry for late response.

Fix for BZ 1403847 just added vertical column borders consistently to all UI table widgets (as well as cleaning up some redundant CSS).

The issue demonstrated in the attached screenshot (consistent 11px grey gap between columns) is likely caused by something else.

(In reply to Greg Sheremeta from comment #6)
> It's caused by there being several 1px wide "hidden" columns there.

That seems to be the likely cause :-)

Comment 8 Michael Burman 2017-08-30 06:10:41 UTC
Verified on - 4.2.0-0.0.master.20170828065003.git0619c76.el7.centos

Comment 9 Sandro Bonazzola 2017-12-20 11:36:21 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.