commit | 91364dbb04e73a7ef9ab8ccf39f76cbf5ae245c7 | [log] [tgz] |
---|---|---|
author | Bao-Duy Tran <tranbaoduy@google.com> | Tue Mar 18 08:54:02 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 18 08:54:02 2025 |
tree | b0ed13e65da5efeee3351c36531acb12920998b8 | |
parent | 220e31c90083d8635a2cc53e4b7862ce84d6e22b [diff] |
Use no-op-AltGr US-Qwerty XKB layout for certain CrOS 1P input methods. These CrOS 1P rule-based (aka. "m17n") input methods remap characters for layouts targeting ISO hardware with AltGr layers. However, they currently use ANSI US-Qwerty XKB layout (without AltGr) as the base. Without true AltGr at XKB level (albeit no-op i.e. no char assignments, just XKB fallback to non-AltGr chars), attempts to implement AltGr at higher m17n layer (atop Alt key events, as currently done) are futile. Such key events can get captured by shortcuts and never reach m17n. This CL must NOT be submitted until https://crrev.com/c/6301430 (landed @ R136-16213.0.0) has been included in CrOS LKGM version [1]. [1] https://crsrc.org/c/chromeos/CHROMEOS_LKGM CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome Bug: b:243243592 Change-Id: Ie5d6cb70db9a31bb14e119e680fa9ba743ad087d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6299674 Reviewed-by: David Padlipsky <dpad@google.com> Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Bao-Duy Tran <tranbaoduy@chromium.org> Cr-Commit-Position: refs/heads/main@{#1434012}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.