| Summary: | [table] IAE (Index out of bounds) after selecting rows in virtual TableViewer | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Stefan Röck <stefan.roeck> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | ||||||
| Version: | 1.1 | ||||||
| Target Milestone: | 1.2 M5 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 256889 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Stefan Röck
Created attachment 115913 [details]
Snippet to reproduce this bug
The content provider reduces the number if items while in updateElement(). The code in AbstractTableViewer#getVirtualSelection() seems not to be prepared for this. Can you confirm that this works in RCP? This doesn't work in RCP (testet with 3.3 and 3.4) either. Would you consider this to be a bug, anyway? It is rather a question whether the platform team would consider this a bug;) I would go ahead and file a bug against Platform/UI and see what they say. If you do so, please re-open with a reference to the related platform bug entry. filed platform bug 256889 Applied the "fix" patch as attached to bug #256889. |