Keyboard output in autopilot tests goes to wrong app
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-keyboard |
Fix Released
|
Critical
|
Tim Peeters | ||
ubuntu-keyboard (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If I run the ubuntuuitoolkit
This issue was confirmed in image 29 and 32 on maguro, and 32 on mako. In all these instances, the tests above pass if no other app is open, and fail when an app was opened before the tests were executed.
After the tests finish to run, some times the app that was open before (like gallery-app) is active and has the keyboard open, even when it currently has a page (the events tab of the gallery) open that does not have keyboard input.
summary: |
- Keyboard output in AP tests goes to wrong app + Keyboard output in autopilot tests goes to wrong app |
Changed in ubuntu-keyboard (Ubuntu): | |
assignee: | nobody → Thomas Moenicke (thomas-moenicke) |
Some analysis:
21:40:43 < Saviq> timp, it looks to me like with the first tap on a text entry field the keyboard gets confused if it's suddenly talking to a different client
21:44:53 < Saviq> timp, so the failure seems to go like so: app with focused text field gets killed -> another app is launched and text field focused -> keyboard gets confused and unfocuses by itself
21:45:06 < Saviq> I'm confirming with manual steps now
21:46:07 < Saviq> timp, actually the fact that another app is focused in the mean time seems to be relevant (since it only happens when another app is running -> and focused when the front one is killed)