After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 744551 - Inconsistent behaviour on touchscreen devices
Inconsistent behaviour on touchscreen devices
Status: RESOLVED OBSOLETE
Product: caribou
Classification: Applications
Component: default
git master
Other Linux
: Normal normal
: ---
Assigned To: caribou-maint
caribou-maint
Depends on:
Blocks:
 
 
Reported: 2015-02-15 06:35 UTC by william.chan4
Modified: 2021-05-25 17:46 UTC
See Also:
GNOME target: ---
GNOME version: 3.13/3.14



Description william.chan4 2015-02-15 06:35:21 UTC
Currently, Caribou is set to always pop up when a text input is selected using a touchscreen. However, this currently only works in the Gnome activity launcher and several core Gnome programs. For all other programs, one has to manually enable the screen keyboard via the accessibility menu in order for Caribou to show after selecting a text input using a touchscreen (such as in Libreoffice Writer and Xournal). This is terribly inconsistent behaviour and a real pain for touchscreen device users.
Comment 1 André Klapper 2015-02-15 08:26:40 UTC
Please provide version information by setting the "Version" field. Thanks.
Comment 2 william.chan4 2015-02-15 13:50:14 UTC
(In reply to André Klapper from comment #1)
> Please provide version information by setting the "Version" field. Thanks.

Done
Comment 3 Geoffrey 2015-10-28 08:56:41 UTC
Hi,

Bug still in gnome 3.18. Workaround, as peviously mentionned, is to activate it in Accessibility Options. However, this leads to having Caribou show up everytime a text input is focused. This can be annoying for user having Hybrid Devices like Lenovo Yoga Pro.
Comment 4 Braden 2016-01-03 21:21:48 UTC
I have a Yoga Pro as well and am running gnome 3.18. However, I can't get the onscreen keyboard to come up even through the accessibility options. I would be fine with that for now as a workaround, as there is a way to get a toggle switch in the top right corner that I can just turn on and off. Ideally it would pop up either when you touch (rather than click) on an input box and/or when the keyboard is disabled (which I also haven't figured out how to do yet).
Comment 5 simon.schumann 2016-01-03 23:22:06 UTC
> Ideally it would pop up either when you touch (rather than click)

That's not a super elegant solution either I think. Reason is that when using a Stylus the keyboard wouldn't come up, for example when placing a text widget in xournal.


I think the virtual keyboard should just stick to the setting in the accessability menu in the top right corner. If the user has a device where it is possible to automatically detect whether a useable hardware keyboard is present, it should just toggle that setting instead of messing with the onscreen keyboard directly in some obscure way.
Comment 6 adrin 2016-04-28 16:45:30 UTC
On Gnome 3.20, using either firefox 46.0, or chromium 50.0.2661.75, I also can't invoke on-screen-keyboard even with accessibility options.

Is there a way to manually, i.e. with a shortcut icon up there - idealy the accessibility option, invoke the keyaboard independent of the application in focus?

Distro: ARCHLINUX
Hardware: Thinkpad X1 Yoga
Comment 7 simon.schumann 2016-05-02 06:25:58 UTC
(In reply to adrin from comment #6)
> Is there a way to manually, i.e. with a shortcut icon up there - idealy the
> accessibility option, invoke the keyaboard independent of the application in
> focus?

I made an extension for that: https://extensions.gnome.org/extension/993/slide-for-keyboard/
Comment 8 froilens 2016-12-04 01:35:26 UTC
I can confirm that this bug exists on Ubuntu GNOME 16.04 with GNOME 3.18 on a non touch screen Toshiba Satellite c645.
Comment 9 André Klapper 2021-05-25 17:46:27 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/caribou/-/issues/

Thank you for your understanding and your help.