Bugzilla – Full Text Bug Listing
| Summary: | [List] Doesn't retain the scroll position after a refresh, instead it scrolls to top | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Claudio Guglielmo <claudio.guglielmo> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P2 | ||||||
| Version: | 2.1 | ||||||
| Target Milestone: | 2.1 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Could be related to this bug 395053 or maybe a duplicate. As a result the client and server are out of sync - List#getTopIndex() return the correct (old) value but the client scrolls to the top (topIndex = 0). Fixed in master with commit d990c73dcf66ed9e657cfc27b92aaeed90456cd2. |
Created attachment 229621 [details] Snippet to reproduce the bug When using a listviewer to refresh a list, the listviewer makes sure that the scroll position is the same as before the refresh (by restoring the topIndex), see AbstractListViewer#internalRefresh. This works well with Rap 1.5 and SWT, but with Rap 2.0 it doesn't work anymore. Instead it scrolls to the top. Little investigation showed, that setTopIndex of the js-list is not called and the topIndex is always 0. See the attached snippet as example.