NoVNC locked on QWERTY despite OS using AZERTY

[rospionne]

Describe the bug
When installing Windows on a virtual machine with the help of NoVNC, I chose the French language and the French keyboard (AZERTY). However, at the end of the installation, when I write in the VM's text editor, it writes in QWERTY. I have checked on the other VMs, this is also the case. The apt update seems to have brought a bug to NoVMC.

To Reproduce
Steps to reproduce the behavior:

1. Configure the operating system to write in AZERTY.
2. Type on the keyboard on a text editor or a field. Especially the letter Z, M.
3. You are forced to write in QWERTY with an AZERTY keyboard

Expected behavior
Permanent problem

**Sreen : **
https://youtu.be/07SheRKUHuk

Client (please complete the following information):

• OS: Ubuntu 20.4
• Broswer: Google-Chrome
• Browser version: Version 92.0.4515.159 (Build officiel) (64 bits)

Server (please complete the following information):
ii novnc-pve 1.1.0-1 all HTML5 VNC client
ii vncterm 1.6-2 amd64 VNC Terminal Emulator

Additional context
NoVNC supports PROXMOX

[rospionne]

See video : https://youtu.be/07SheRKUHuk

[CendioOssman]

I'm afraid such issue are pretty much always a server issue, so it's not something we can fix in our end. Have you reported this issue to proxmox?

[rospionne]

Ticket create on https://bugzilla.proxmox.com/show_bug.cgi?id=3634
Reddit : https://www.reddit.com/r/Proxmox/comments/psl072/bug_proxmox_locked_in_qwerty_with_an_azerty/

why this bug is present on Chrome and not on Firefox ? Why is it present when interacting with VMs, but not with nodes using noVMC ?

[flumm]

it seems to be a chrome/chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1245196&q=keyboard%20layout&can=2

[CendioOssman]

Nice find. If it is indeed a bug in the browser then it will be impossible for us to fix it in our end. :/

@rospionne, could you test if you get the buggy behaviour with Chrome here: https://w3c.github.io/uievents/tools/key-event-viewer.html

[rospionne]

Indeed, when I do Shift + 1, the result is !. While the expected result is 1.

[CendioOssman]

Then unfortunately we can't proceed from our end and we'll have to wait for Chrome to fix this. It seems to be a recent regression so hopefully they'll prioritize a fix.