GNOME Bugzilla – Bug 663015
GNOME Onscreen keyboard
Last modified: 2014-08-07 11:04:03 UTC
I am a tablet user, Toshiba portége m750. The problems described here are all about the new GNOME 3.2 onscreen keyboard. - One of my custom buttons on the laptop I have programmed to start the onscreen keyboard. When the onscreen keyboard starts onboard is also started. Currently you can solve this problem by removing onboard. However this is not a perfect solution in my opinion. - Situation: after I started the onscreen keyboard, it is possible to reveal it by pressing the 'keyboard' icon in the tray bar. Now I want to program a button on my keyboard such that the onscreen keyboard is revealed there is no functionality yet for this. (I can program a button to start the onscreen keyboard but not to reveal/disappear the actually keyboard) - The location of the onscreen keyboard icon in the tray bar is very inconvenient. You have to bring up the tray bar to press the icon. The problem is is that most tablets are not very accurate on the very sides of the screen, further it is hard to aim with your finger, hence bringing up the onscreen keyboard by hand is very hard. A more convenient way would be that there would be a floating icon on the screen (on top of everything else) to bring up onscreen keyboard. Or a more permanent location, such as the topbar would improve the usability a lot. - Currently the onscreen keyboard does not always turns up when you are focused on a text entry field. For example when you are visiting websites in your browser and want to fill in a form, you have to manually bring up the onscreen keyboard. Of course this is not very handy.
This bug belongs to gnome-shell and/or gnome-settings-daemon.
Which distribution is this about? Also, please only file one issue per report, otherwise it is impossible to handle it. See https://bugzilla.gnome.org/page.cgi?id=bug-writing.html
Ubuntu 11.10. Sorry about the multiply issues. But I just wanted to report some feedback and I couldn't find any form, so I posted it here on bugzilla in the accessibility section. Should I post all the issues (feedback) I have in new bugreports?
(In reply to comment #3) > Should I post all the issues (feedback) I have in new bugreports? Yes, please. But before doing so, have a look at the existing reports to see whether your issue has already been reported.
Has the reported filed multiple bugs for these issues?
(In reply to comment #5) > Has the reported filed multiple bugs for these issues? Looking at his user page shows he hasn't (hopefully) yet.
In the long run, I don't think that the manual keyboard button is something we really want - the keyboard should always automatically pop up when you focus a text entry widget. I'm pretty sure that the issues with the keyboard not automatically popping up are being tracked elsewhere, such as bug 709935, so marking this as a dupe. *** This bug has been marked as a duplicate of bug 709935 ***