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)
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).
(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.)
(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.
(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.
Verified on ovirt-engine-3.6.0-0.0.master.20150713172442.gitd6e83be.el6.noarch