OSK does not get displayed after a suspend/resume

[Pat McGowan]

This is seen in build 250 and 287

Open Notes, select the text field and OSK is displayed
Allow the phone to timeout and suspend
Push power to resume, open the greeter
The OSK disappears and cannot be restored in the app

The same happens in Riddling, but selecting other tabs reveals the OSK (when that should actually hide it)

In calendar, edit a new event, select a field like description, allow the unit to suspend.
When it comes back you can no longer select the description field to see the osk, but selecting any other field will reveal it.

This does not happen in other apps (browser, terminal, messages, contacts, clock)

[Pat McGowan (pat-mcgowan)]

Also affecting SDK since focus of the text field seems to be involved

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael Sheldon (michael-sheldon)]

Had a quick poke at this, it seems the QML components in question still think they have focus, but the maliit framework is telling the ubuntu-keyboard plugin that focus has been lost. Not clear yet whether this is a problem with maliit's focus detection or something elsewhere though.

[Pat McGowan (pat-mcgowan)]

There are some fixes in silo 9 that reportedly fix this
perhaps https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/textinput-focus-fix/+merge/217909

[Michael Sheldon (michael-sheldon)]

Retesting this on image #63 this now appears to be resolved. Now when the unit suspends focus is removed from the field allowing the user to select the field again to reopen the keyboard; so marking this as fixed.

[Julia Palandri (julia-palandri)]

In #85 my keyboard still disappears after I turn off the screen.
For example:
1. open telegram
2. select a conversation
3. touch the text field. the keyboard will pop up.
4. turn the screen off.
5. turn the screen on. the keyboard is gone, and if you tap on the text field it will still not show up again.
6. if you go further selecting other conversations and going back and forth, the keyboard will appear for the new conversation selected, but after going back to the list, it will still be there (when there's no need for it.