Chromium

possibly related / dupe: crbug.com/407944200

Hi all, adding more examples of keyboard issues in Linux:

Affected Chrome Version(s):
135.0.7049.52

Affected Operating Systems:

• Linux: 6.12.17
• Linux: 6.12.12
• Linux: 6.11.0-21
• Linux: 5.15.0-136
• Linux: 6.8.0-57

Issue Description + Insights/Patterns:

Users report that the keyboard isn’t working for those who use languages other than English, with an emphasis on special characters and keyboard layouts not working. Some users also indicate that backspace, enter, and arrow keys aren’t working as well.

Special character & custom keyboard issues:

• https://listnr.corp.google.com/product/237/report/92420196730 (Da, special characters via AltGr not working)
• https://listnr.corp.google.com/product/237/report/92420315715 (Da, special characters via AltGr not working)
• https://listnr.corp.google.com/product/237/report/92419974598 (Googler report, custom keyboard layout not recognized)
• https://listnr.corp.google.com/product/237/report/92419902426 (Neo 2, custom keyboard layout not recognized)
• https://listnr.corp.google.com/product/237/report/92420666253 (Sp, custom keyboard layout not recognized)
• https://listnr.corp.google.com/product/237/report/92420524230 (Fr, custom keyboard layout not recognized

Backspace, enter, and arrow keys not working:

• https://listnr.corp.google.com/report/92419857947 (Ko)
• https://listnr.corp.google.com/report/92419388979 (Ko)
• https://listnr.corp.google.com/report/92419719119 (Ko)

Fix is up here: https://chromium-review.googlesource.com/c/chromium/src/+/6426564

With that, as long as the wayland IME is enabled (through the wayland dogfood or manually enabled from chrome://flags/#wayland-text-input-v3) it should work again.

but that change isn't submitted yet. How can it be working on Chrome 136 without that then? Or is that somehow just the backport of the original fix that already landed in 136?

For me it's broken in M136 as well.

Git bisect revealed that it broke due to https://chromium-review.googlesource.com/c/chromium/src/+/6310469 which was introduced in M135 and is there in M136. So I would expect this bug to also be present in M136.

Project: chromium/src
Branch: main
Author: Orko Garai orko@igalia.com
Link:      https://chromium-review.googlesource.com/6426564

Don't use GTK IME if WaylandTextInputV3 feature is enabled

     
    GTK4 was enabled by default on gnome as per https://crrev.com/c/6310469 
    which introduces the GTK IME (InputMethodContextImplGtk). But that one 
    is more of a fallback which doesn't include a CharacterComposer and so 
    it breaks AltGr/Dead key use cases. 
     
    If WaylandTextInputV3 feature is enabled, use that instead, which 
    enables the WaylandInputMethodContext IME, that supports a character 
    composer. 
     
    Fixed: 407944200, 407930251 
    Change-Id: Idfa6326c1a03008749cca49be5889c93e7babed6 
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6426564 
    Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> 
    Commit-Queue: Orko Garai <orko@igalia.com> 
    Cr-Commit-Position: refs/heads/main@{#1441738}

Updating the priority from issue 407944200.

Hah! I believe my Chrome 136 was running under XWayland and that is probably why it worked.

When will this fix be in a release, and which release will it be? Do I have to install google-chrome-beta?

Not fixed on 135.0.7049.52 (Official Build) (64-bit) for AltGr characters.

Example:

• Keyboard layout: Polish
• Keys pressed: AltGr + a
• Result: a
• Expected result: ą

Added 135 and 136 to the Merge-Request field, not sure if that is enough to get the backporting started…?

M135 merge request created. Please update crbug/408167146 to have this merge reviewed.

M136 merge request created. Please update crbug/408166865 to have this merge reviewed.

ok, seems like that was enough. I've filled the required fields in the merge request bugs ttbomk.

re #comment12: I believe you're not on Wayland. Iiuc the issue only affects Wayland. Both XWayland and X11 seem to not be affected.

Thanks mteich@ for requesting the merge requests. It seems it just became available on canary 137.0.7106.0.

I will prepare the merges to M135 and M136 now.

The status of landed versions can be followed here: https://chromiumdash.appspot.com/commit/6e5b9d89fc353c2f0b9d71085095d0a0976def8b

Just tested on 137.0.7106.0 and fix works there. Canary builds for some distros can be downloaded here: https://www.google.com/intl/en_ca/chrome/canary/ if others want to try it.

I just tried launching google-chrome-canary --ozone-platform=wayland, reporting "Version 137.0.7106.0 (Official Build) canary (64-bit)", and I still had the issue.

Actually, it works if I explicitly enable WaylandTextInputV3 in chrome://flags, so that case seems resolved, but there may be a broader issue.

re #comment23:

Yes IME is still not officially supported in ozone/wayland, but has been reported to work better with the experimental WaylandTextInputV3 feature on gnome.

If you don't use WaylandTextInputV3 it is now falling back on GTK IME which has limitations like this issue (and popup issues) and is not recommended.

The Google internal wayland dogfood enables the WaylandTextInputV3 for this reason. The part that broke was it was still using the GTK IME even when WaylandTextInputV3 was enabled, which should be fixed now with the above landed fix.

I see. Indeed running with --disable-gtk-ime --ozone-platform=wayland seems to also work with 135.0.7049.52 and 136.0.7091.2 (before the fix), even with --disable-feature=WaylandTextInputV3

Project: chromium/src
Branch: refs/branch-heads/7103
Author: Orko Garai orko@igalia.com
Link:      https://chromium-review.googlesource.com/6431107

[M136] Don't use GTK IME if WaylandTextInputV3 feature is enabled

     
    GTK4 was enabled by default on gnome as per https://crrev.com/c/6310469 
    which introduces the GTK IME (InputMethodContextImplGtk). But that one 
    is more of a fallback which doesn't include a CharacterComposer and so 
    it breaks AltGr/Dead key use cases. 
     
    If WaylandTextInputV3 feature is enabled, use that instead, which 
    enables the WaylandInputMethodContext IME, that supports a character 
    composer. 
     
    (cherry picked from commit 6e5b9d89fc353c2f0b9d71085095d0a0976def8b) 
     
    Bug: 407930251 
    Fixed: 408166865 
    Change-Id: Idfa6326c1a03008749cca49be5889c93e7babed6 
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6426564 
    Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> 
    Commit-Queue: Orko Garai <orko@igalia.com> 
    Cr-Original-Commit-Position: refs/heads/main@{#1441738} 
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6431107 
    Auto-Submit: Orko Garai <orko@igalia.com> 
    Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> 
    Cr-Commit-Position: refs/branch-heads/7103@{#140} 
    Cr-Branched-From: e09430c64983fc906f37a9f7e6806275c9b67b86-refs/heads/main@{#1440670}