Context long press

[GoogleCodeExporter]

I use WiFi Keyboard 2.2.1

When pressing the return key of the PC for a long time, in some Android 
programs a context sensitive menu will open. 

The behaviour is not as expected. Two different kinds of malfunctions can be 
observced:

1) It seems that the "focus" is not at the foreground menu but stays "behind" 
the new foreground menu.
Example: 
With the program "Task List - ToDo List" (LorSoft), Version 2.5 
(http://anddev.intbuilder.com/tl/faq.aspx) some actions for the different tasks 
can be selected by using the context long press. But pressing the cursor 
up/down keys at the PC afterwards, still the navigation is with regard to the 
tasks, but not within the context menu.

2) Using Google Mail and pressing the return key when being in the list of 
mails, the context menu opens for a short moment. Afterwards, immediately the 
email is opened. The context menu disappears beforehead.

------------------

My expectation is that pressing the "return" key at the PC would just open the 
context menu as it is the case when doing it with the phone (and navigation is 
possible). It would be ok if the functionality would be achieved with another 
key press (function key F8 or something similar) 

I observe this with a HTC dream (G1) and using the Android 1.6 based 
CyanogenMod 4.2.15.1 .

Original issue reported on code.google.com by topas081...@googlemail.com on 19 Feb 2011 at 9:00

[GoogleCodeExporter]

My understanding is that the missing focus to context menu is android bug. I 
didn't found a way how to workaround it.

Original comment by Ivan.Volosyuk on 20 Feb 2011 at 6:26

• Changed state: Accepted

[GoogleCodeExporter]

Hi Ivan,

thanks for your fast analysis. 

Is it possible that we create an issue against android?

I am not kidding ;-) I think in the middle term, it should be possible that the 
android software is able to put the focus right there where the "most 
prominent" item is visibile on the screen. Well, it is just software, isn't 
it?.... ;-)

Could you (as the owner of wifikeyboard and the person that is best involved in 
the technical details) perhaps open such an issue against android?

If yes, could you just inform me about the tracking id or the url of the bug?

Thanks in advance,

Topas.

Original comment by topas081...@googlemail.com on 2 Mar 2011 at 4:46