Bug 1140249

Summary:	The Details pane sizing information isn't maintained
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gilad Lazarovich <glazarov>
Component:	ovirt-engine	Assignee:	Alexander Wels <awels>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.5.0	CC:	acanan, gklein, lsurette, rbalakri, Rhev-m-bugs, srevivo, vszocs, ykaul
Target Milestone:	ovirt-3.6.0-rc
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-20 01:30:09 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:

Description Gilad Lazarovich 2014-09-10 15:02:28 UTC

Description of problem:
The Details pane sizing information isn't maintained

Version-Release number of selected component (if applicable):
3.5 vt2.2

How reproducible:
100%

Steps to Reproduce:
1. Navigate into any Resource tab such as Virtual Machines
2. Click on Any VM
3. Change the Details pane sizing
4. Unselect and then re-select the same VM

Actual results:
The Details pane sizing returns to the default size

Expected results:
The sizing information should be maintained (at least across the session and the Resource tab selected)

Comment 1 Einav Cohen 2014-10-21 12:42:55 UTC

need to persist in a cookie/similar (i.e. similarly to persisting the grids columns widths, for example) the last height of the details pane (there should be a single 'last height' value cross-GUI - don't keep the last height value per main-tab or anything like that).

Comment 2 Vojtech Szocs 2014-11-24 17:39:07 UTC

(In reply to Einav Cohen from comment #1)
> need to persist in a cookie/similar (i.e. similarly to persisting the grids
> columns widths, for example) the last height of the details pane (there
> should be a single 'last height' value cross-GUI - don't keep the last
> height value per main-tab or anything like that).

What's the motivation for not implementing per-tab-detail-pane height across different main tabs? (Assuming different main tabs have different detail panes with different height, plus assuming that different main tabs show different volumes of data.)

Comment 3 Einav Cohen 2014-11-25 15:58:54 UTC

(In reply to vszocs from comment #2)
> (In reply to Einav Cohen from comment #1)
> > need to persist in a cookie/similar (i.e. similarly to persisting the grids
> > columns widths, for example) the last height of the details pane (there
> > should be a single 'last height' value cross-GUI - don't keep the last
> > height value per main-tab or anything like that).
> 
> What's the motivation for not implementing per-tab-detail-pane height across
> different main tabs? (Assuming different main tabs have different detail
> panes with different height, plus assuming that different main tabs show
> different volumes of data.)

my hunch is that the better user experience in this case would be a consistent sub-tab panel height across the system rather then persisting the height per main-tab; I think that the user perceives the sub-tab panel as a cross-GUI component, rather then a separate component per main-tab.

Comment 4 Vojtech Szocs 2014-11-28 17:12:13 UTC

(In reply to Einav Cohen from comment #3)
> my hunch is that the better user experience in this case would be a
> consistent sub-tab panel height across the system rather then persisting the
> height per main-tab; I think that the user perceives the sub-tab panel as a
> cross-GUI component, rather then a separate component per main-tab.

Yes, that makes a lot of sense. I tend to see GUI from too-much-technical perspective.

I've also talked with one of QE guys and he confirmed what you wrote above.

Comment 5 Petr Matyáš 2015-07-14 11:40:12 UTC

Verified on ovirt-engine-3.6.0-0.0.master.20150713172442.gitd6e83be.el6.noarch