Bug 277600 - [content assist] Autocompletion list view of content assist doesn't allow letter navigation
Summary: [content assist] Autocompletion list view of content assist doesn't allow let...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-24 04:11 EDT by Sérgio Neves CLA
Modified: 2019-09-06 16:04 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sérgio Neves CLA 2009-05-24 04:11:40 EDT
Build ID: M20090211-1700 

Steps To Reproduce:
1. In any editor (for example, java editor) type
String s = "abc";
s = s.<control space><tab> to present and focus the autocompletion list view of string methods.
2. Press any character to go to a method that starts with this character, for example 't' to go to the first method that starts with 't' (in my case is toLowercase()).

Expected result: focus should go to the method that starts with the characters typed.
Actual result: focus remains in the first method of the autocompletion list.

More information:
In other list views, such as menu help -> about eclipse sdk->feature details I'm able to navigate by characters.
Comment 1 Dani Megert CLA 2009-05-25 08:03:52 EDT
This happens because we use a SWT.VIRTUAL table.

The behavior makes sense to prevent eager loading of the items when a key is
pressed.

Steve, is there a way to workaround this on our side?
Comment 2 Steve Northover CLA 2009-05-25 11:57:46 EDT
Not really, other than add the key listener.  However, plaforms such as GTK have really funky popup that allows type ahead.  The real fix would be to add API to enable searching in the model.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:04:10 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.