Open Bug 1728677 Opened 2 years ago Updated 2 years ago

[wayland] Touchscreen tap after 10 second toggles screen keyboard

Categories

(Core :: Widget: Gtk, defect, P3)

Product:
Core
Component:
Widget: Gtk
Version:
Firefox 91
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: mtogop, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

I have squeekboard set up to automatically show when a text field is selected. Squeekboard toggles unexpectedly after the steps below. I tested with other applications, and the bug seems Firefox-specific, hence I'm filing it here.

  1. Tap the screen outside a text box (squeekboard disappears as expected)
  2. Wait 10 seconds (9.5 seconds doesn't trigger the bug, 11 consistently does)
  3. Tap again outside a text box.

Distro: Arch
Firefox version: 91.0.2
Wayland compositor: sway 1.6.1
Screen keyboard: squeekboard (https://gitlab.gnome.org/World/Phosh/squeekboard/)
Device: Surface Book 1 detachable laptop

Actual results:

Squeekboard appeared. Waiting additional 10 seconds and tapping again causes squeekboard to disappear.

Expected results:

Since no text field is selected, squeekboard shouldn't toggle itself.

Tapping with the trackpad with one or two fingers; two-filger scrolling; pinching; or tapping with the surface pen; also causes the issue.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Priority: -- → P3

I couldn't try it as described in the guide, as squeekboard doesn't run on mutter (or kwin). I tested in a full gnome-session with Gnome's screen keyboard, and it doesn't seem to be an issue there - but that keyboard seems to work differently (for example, as if to overcompensate, I need to click twice on the URL bar for it to show up).

Flags: needinfo?(mtogop)
You need to log in before you can comment on or make changes to this bug.