events propagating to windows beneath keyboard
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-keyboard (Ubuntu) |
Fix Released
|
Critical
|
Gerry Boland |
Bug Description
--pending build 20130827.1
Galaxy Nexus, using Surface Flinger (default build)
ubuntu-keyboard 0.99.trunk.
Seeing weird issues with the keyboard. Seeing problems since this MR has landed:
https:/
I don't see the problem with using earlier versions of ubuntu-keyboard.
Specifically typing in the keyboard is causing it to either automatically close or propagate events to areas beneath it incorrectly.
Steps to reproduce:
1) Open contacts app
2) swipe up keyboard and press "Add"
3) Try to type first name and/or last name. Press the "shift" key to capatalize the first letter.
Expected Results:
- keys are entered correctly, entry field that you were typing in remains focused, keyboard remains visible
Actual Results:
- very often (but not every time) pressing the shift key will cause the keyboard to disappear. Or sometimes when starting to type the name the cursor jumps to one of the fields that lives under the keyboard and this is scrolled into view.
Other steps:
- if you can't reproduce it in the above method, just try entering a phone number and type quickly in the phone number field, or email field. quite often you can get the cursor to jump to another field underneath the keyboard and the typing continues there.
Related branches
- Bill Filler (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 13 lines (+3/-0)1 file modifiedsrc/plugin/ubuntuapplicationapiwrapper.cpp (+3/-0)
Changed in ubuntu-keyboard (Ubuntu): | |
importance: | Undecided → Critical |
assignee: | nobody → Gerry Boland (gerboland) |
Changed in ubuntu-keyboard (Ubuntu): | |
status: | New → Confirmed |
Changed in ubuntu-keyboard (Ubuntu): | |
status: | Fix Released → Confirmed |
Yep, my fault. I broke the hacky logic to detect if platform-api was available (it is actually checking if Open GL ES 2 is available in Qt, if yes platform-api should be there, if not then on desktop).
The logic is pretty nasty, but I don't think it's worth spending lots of time on it until after transitioning to Mir on phone (at which time, that compability layer can go away)