Onboard onscreen keyboard isn't always shown when text input selected

Bug #1071508 reported by Chris Wayne on 2012-10-25
42
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Onboard
Undecided
Unassigned
ubuntu-nexus7
Medium
Unassigned

Bug Description

Image: 20121025-3

Summary:
Onboard is supposed to show up automatically whenever a text field is selected, however this is not always happening. Sometimes a text input is selected, and the user must open onboard manually through the indicator

Chris Wayne (cwayne18) on 2012-10-26
information type: Proprietary → Public
tags: added: nexus7
affects: newark → ubuntu-nexus7
marmuta (marmuta) wrote :

Thanks for your bug report. Is it that auto-show is unreliable everywhere the same, or does it fail consistently with certain applications?
If it's the latter and you want us to have a closer look, please post the applications and brief instructions how to find the text entries where it fails. Check out (potential duplicate) bug #936310 for a previous list, though I'm sure there are a lot more. Many applications support GNOME Accessibility out of the box, but there are a large number of old, and to a lesser extent new ones, that don't.

Changed in onboard:
status: New → Incomplete
Mirzet Kadic (caracal-enl) wrote :

Hi Guys

I think this bug report is justified. I tried to reproduce it and recorded it as a video using Kazan Screencaster:
http://youtu.be/kUvq2epiylM
Okay, the video is not very helpfull because of performence.

Case 1
If you are editing a simple text document and you closed the keyboard accidently, you can not just retouch in the inpit-field to re open the keyboard. You have to touch somewere else and than back in input-field to reopen it.

Case 2
"Save as" dialog. If you editing the name of the file that you wont to save and you closed the keyboard again accidently, you can not just re-touch in the inpit-field to re open the keyboard.

I hope this helps....

marmuta (marmuta) wrote :

Caracal, that's an interesting suggestion, but we could track it better as a separate bug report. Would you mind opening a new one? I'd like to see this implemented, though I'm not sure if this is currently possible.

Mirzet Kadic (caracal-enl) wrote :

I don't have any experience handling bug reports, I think you should do what you think is the best way.

marmuta (marmuta) wrote :

Mirzet, I've opened a bug report for you here:
https://bugs.launchpad.net/onboard/+bug/1078602

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers