Description Sebastien Arod 2011-06-22 09:55:24 EDT

Build Identifier: 

Investigating usage of Content Proposal in our application I found several bugs/difference in behavior between RAP and RCP regarding this feature.

Here is a summary of the problems I found.

1. Key strokes with modifiers does not trigger the proposal(CTRL+SPACE for instance)

2. Using '.' in autocompletion characters only trigger proposal if '.' is accessible with a single key on the keyboard. (on french keyboard CAPS LOCK has to be enabled first) SHIFT+[;/. key] does not trigger proposal

3. Description of proposals are randomly synchronized with the focused proposal.

4. Proposals does not appear at cursor location. This is especially problematic when using multiline text.

5. In RCP when the proposal is displayed it gain partial focus so that keyboard arrows can be used to select the proposal. This doesn't work in RAP. In Firefox pressing TAB give the focus to the popup but even this doesn't work in Chrome.


I'm using RAP 1.4 RC3 on Chrome 12 and Firefox 4

I created a small project that I will attach reproducing the described issues. 




Reproducible: Always

Steps to Reproduce:
See attachment