Bug 1172380

Summary: [RFE] [engine-webadmin] refresh view is rolled up to the list head
Product: [Retired] oVirt Reporter: Einav Cohen <ecohen>
Component: ovirt-engine-webadminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kubica <pkubica>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5CC: awels, bugs, ebenahar, ecohen, gklein, iheim, lsurette, mgoldboi, nbarcet, pstehlik, rbalakri, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: 3.6.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: ux
Fixed In Version: ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1046279 Environment:
Last Closed: 2015-11-04 13:52:43 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:
Bug Depends On: 1046279    
Bug Blocks:    

Description Einav Cohen 2014-12-09 23:45:51 UTC
+++ This bug was initially created as a clone of Bug #1046279 +++

Description of problem:
When we roll down to the bottom of a list in the UI (of VMs for example) which is longer than the screen capacity and then we refresh the view, the view will be rolled up to the head of the list instead of preserve the last location in the view before the refresh.

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

How reproducible:

Steps to Reproduce:
1. have a VMs list which is longer than the screen capacity (so it will be possible to roll down) and roll down to the bottom of the list
2. refresh the list

Actual results:
The view is rolled up to the top of the list.

Expected results:
The view should be rolled down to the last location it was before the refresh.

Comment 1 Petr Kubica 2015-05-06 13:46:04 UTC
Verified in 3.6.0-0.0.master.20150504172354.git5d5237f.el6

Comment 2 Sandro Bonazzola 2015-11-04 13:52:43 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.