Last modified: 2012-12-14 11:13:50 UTC
I remember it was possible to do it just as if I'm using a standard Android browser.
Yeah, this may have happened when we moved from iframes to divs for the holder... possibly something is preventing keyboard navigation in the parent document (which would be damned annoying!)
Should we target hardware keyboard support in 1.2?
Should we target hardware keyboard navigation support in the near future at all?
As long as enter works to search i dont minding punting on this for now. There are only a handful of Android handsets that have dedicated keyboards.
Not doing this until webkit on android gets proper support for keyboard navigation hints.
Closing as "WONTFIX" (developers do not plan to fix this) to get rid of the deprecated "LATER" resolution and to provide a realistic outlook - unfortunately developer manpower and time is limited, sorry. In case you feel that this really must get fixed your contributed patch is highly welcome.