Comment 4 for bug 1323743

I'm now able to actually reproduce with even fewer steps, just opening twitter and visiting an external link, then swiping right is enough to trigger it. The keyboard doesn't even need to have been shown beforehand.

It seems oxide is sending visibility change requests correctly when the focused node changes, however the keyboard plugin never receives them, so I'm now taking a look at the maliit framework to try and work out what happens in between to cause the request to go missing.

Interestingly if the maliit-server is restarted after the bug has been triggered the keyboard will start displaying in the twitter webapp again.