Keyboard is hard to use on Manta, and occasionally hard to use on flo

[John McAleely]

Flash a nexus 10 with the current MWC demo image (https://wiki.canonical.com/JohnMcAleely/MWCDemoNotes)

(It will probably fail to push the video content. That doesn't matter for this bug)

Boot device
Dismiss greeter, with 'tap to unlock'

Find a place to use the keyboard. A good choice is to swipe down the notification, and attempt to join a wifi network.

Enter your wifi password

In my experience, one of the buttons will fail to respond. It seems to vary, but I feel it is more common on buttons on the top row.

A common (but not 100% symptom) is that the button pop up showing the letter tapped stays stuck on screen, but the letter is not recorded.

[John McAleely (john.mcaleely)]

This has also been observed on flo, but seems much rarer. Retitled to reflect

[John McAleely (john.mcaleely)]

I guess this is against the wrong project, but I've been unable to locate the correct one. Sending this bug in the right direction would be much appreciated. Sorry for the hassle

[Pat McGowan (pat-mcgowan)]

The hit points for the keys are too low, so on the top row hitting just above the letter results in no character.
Try hitting high on a letter in the second row, and you get a letter in the top row (i.e. you can hit within the key for a d and get an e)
Seems that the hit area is not the same as the key.

[Pat McGowan (pat-mcgowan)]

Also note that the location of the OSK is not at the bottom of the screen, but offset up by several pixels.

[Gerry Boland (gerboland)]

This is a bug in qtubuntu, not in the OSK itself.

The OSK is a fullscreen surface. I think in lp:qtubuntu:/src/ubuntu/ubuntucommon/screen.cc that the availableGeometry() or geometry() values are incorrect for manta - causing positioning and input events to be mis-calculated. Regression most likely caused by changes made for Flo.

Please give more info on the Flo keyboard problems.

[Olli Ries (ories)]

re comment #3) does this apply to manta & flo?

[kevin gunn (kgunn72)]

video to help explain

http://www.youtube.com/watch?v=B89qXqbBL9Q

[Gerry Boland (gerboland)]

Upon a little more research, I deduced the fault to unity-mir's surface placement logic - not qtubuntu's internal geometry.

OSK surface needs to be positioned underneath the panel (0, 67). But ApplicationManager::placeSession was positioning it at (0,0), since it didn't recognize it as an application surface.

If unity-mir places a surface in a position where the app doesn't expect it to be, input events get confused, causing these key mis-hit issues.

[Gerry Boland (gerboland)]

Ok, I've linked a branch that I believe fixes this issue. I'm now scoping out testers...

[Pat McGowan (pat-mcgowan)]

Filed related bug #1282133