Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 320602

Summary:	[Tree] Improve performance of keyboard-navigation in big trees
Product:	[RT] RAP	Reporter:	Tim Buschtoens <tbuschto>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	tbuschto
Version:	1.3
Target Milestone:	1.4 M1
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	320597

Description Tim Buschtoens

2010-07-22 05:21:36 EDT

In a big Tree, keyboard navigation is noticeably slower at the bottom than at the top. This is due to the way "_findIndexByItem" works. We should find a way to optimize that function.

Comment 1 Tim Buschtoens

2010-07-30 12:26:10 EDT

Fixed in CVS HEAD by refactoring findIndexByItem and key-handling in general in Tree.js. Keyboard-navigation in IE6 is still kinda slow (especially when holding down a key), but i think that is mostly rendering and therefore another issue. Any further optimization in the internal model-navigation logic would require caching more data, e.g. the focusItem index.