On-screen keyboard shows up on first touch even when touch does not activate a text-field

[Andrea Azzarone]

Impact
======
Copied from: https://bugzilla.gnome.org/show_bug.cgi?id=788188

"After using the keyboard (or bluetooth stylus), the first touch gesture I make on the touchscreen always brings up the on-screen keyboard, irrespective of whether the touch activates a text-field. This is annoying, for instance when I am using the touchscreen on the maps app (which is much more convenient than from the touchpad), or when I am using the stylus and want to use a touch-screen gesture to scroll to the next page."

Test Case
=========

Regression Potential
====================

Workaround
==========
https://extensions.gnome.org/extension/1326/block-caribou/

[Sebastien Bacher (seb128)]

The upstream bug has a candidate patch

[tom (tombuntus)]

It's a regression bug that did not exist in GNOME versions prior to 3.26. It shouldn't need patching, but to simply un-do the anti-progress between 3.24(I'm not sure exact version) and 3.26.

[Tristram Oaten (0atman)]

IMO this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+bug/1723857, as there's far more activity on it.

[tom (tombuntus)]

Thanks Tristram. I wrote the same thing, but the powers that be still haven't even responded. This bug is paper-thin compared to 1723857.

[PJSingh5000 (pjsingh5000)]

Do we know what the desired behavior requirements are?

I'm thinking something like...

1. User taps screen
2. Check if event is in an editable text area
3. If yes, display caribou in half* of the screen where tap did ~not~ occur
4. If no, do not display caribou
5. If caribou is not displayed, sliding up from the bottom of the screen should always be available in order to activate the on-screen keyboard.

(* Perhaps this could actually be changed to: display caribou in the quadrant of the screen diagonal to where the tap occurred. But you have to take screen size into account, so for smaller screens, the half screen rule above may need to be used).