<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=435632) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!-- Summarize the bug encountered concisely. --> It seems with the AZERTY keyboard layout, some keyboard shortcuts are not working as expected and are mapped incorrectly. This has come up in a support ticket (linked in first comment). In this case, with an AZERTY keyboard, `CMD + Z` is wrapped to `CMD + W` (MacOS). `CMD + Z` for undo functionality will close the current tab, which one would expect when your press `CMD + W` - this is not the same behavior with VS code locally. `CMD + Z` locally in VS Code will `undo`. The layout at the bottom right has to match the keyboard layout for the shortcut to function correctly, for example with azerty, you have to pick `fr` (azerty). ### Steps to reproduce <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> I don't have a physical AZERTY keyboard, I have QWERTY (ubuntu), but was still able to reproduce when I changed my OS level layout to `fr` (azerty). - switched the OS level layout to ``AZERTY`` (so my Q on the QWERTY physical keyboard was now an A, W was Z and so on...) - opened the IDE, the default was layout on the bottom right was `us`. - wrote some text and tried to undo with `ctrl+w` (the physical key W which now mapped to Z, so I was doing a `ctrl+z` according to the OS). The Web IDE tab was closed. - I switched the layout at the bottom right from `us` to `fr` and tried `ctrl+w` (again, the OS knows this is `ctrl+z`). This time, the undo functionality worked. ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? <!-- Describe what actually happens. --> Some keyboard shortcuts are not matched correctly on AZERTY keyboard ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> Keyboard shortcuts should be mapped correctly regardless of the keyboard layout. ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ### Output of checks <!-- If you are reporting a bug on GitLab.com, uncomment below --> <!-- This bug happens on GitLab.com --> <!-- /label ~"reproduced on GitLab.com" --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->