Keyboard shortcut issues with a different keyboard layout (os level or physical) like AZERTY

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

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

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

What is the current bug behavior?

Some keyboard shortcuts are not matched correctly on AZERTY keyboard

What is the expected correct behavior?

Keyboard shortcuts should be mapped correctly regardless of the keyboard layout.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(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`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(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)

Possible fixes