Steps to reproduce: 1. Open the hardware keyboard. 2. Tap in the awesomebar and start typing. Expected results: Awesomescreen results update as you type. Actual results: Awesomescreen results update only for the first character typed, or whenever you press backspace. Tested on local trunk Android build.
The "keydown" events are not sent to Gecko, because mKeyListener.onKeyDown returns "true" in GeckoApp::onKeyDown.
(In reply to comment #1) > The "keydown" events are not sent to Gecko, because mKeyListener.onKeyDown > returns "true" in GeckoApp::onKeyDown. Of course, keydown events aren't the only thing that can trigger awesomebar updating. After all, almost no key events are sent when typing with many soft keyboards. The difference is that the text events during softkb composition are sent during composition, while the text events sent through the hardkb listener are sent without composition. Wonder if that makes the difference. Maybe jchen knows.
Created attachment 493035 [details] [diff] [review] WIP mwu suggested starting and stopping coposition to force an update. Here's an implementation of that suggestion. It fixes this bug, but I'm not sure if it's the correct way to do it.
Created attachment 493051 [details] [diff] [review] patch Here's a better patch, with much help from jchen. Makes sure that the text event happens between composition begin/end events.
Attachment #493051 - Flags: review?(blassey.bugs) → review+
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
verified FIXED on build: Mozilla/5.0 (Maemo; Linux armv71; rv:2.0b8pre) Gecko/20101129 Namoroka/4.0b8pre Fennec/4.0b3pre
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.