[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

I feel like that's a separate bug, but on the same critical path to getting the OSK working. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland,

[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

In addition to not showing up automatically, the wrong text is selected. ** Attachment added: "https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990253;

[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland, the onscreen keyboard does not

[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland, the onscreen

[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

per test on jammy updated on 2022/03/28, wayland mode, OSK works fine with firefox snap (v98.0.2-1, r1154) ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: 2-in-1 ** Tags added: oem-priority -- You received this bug notification because you are a member

[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

Firefox does do some things differently to what I would refer to as an "GTK app" so I don't count Firefox as a GTK app even though it uses some GTK. Using Xwayland may be a common factor but that's probably more of a correlation than causation. Anything that's not yet ported to native Wayland

[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

Firefox uses GTK, but in a Wayland session it runs on XWayland, the same for Qt apps and Chrome, they run on XWayland in a Wayland session. That's a common factor. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => Low -- You received this bug notification because