Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hotkey issue in Browser (azerty vs querty) #11065

Closed
dbriard opened this issue Apr 19, 2023 · 1 comment · Fixed by #12549
Closed

Hotkey issue in Browser (azerty vs querty) #11065

dbriard opened this issue Apr 19, 2023 · 1 comment · Fixed by #12549
Labels

Comments

@dbriard
Copy link
Contributor

dbriard commented Apr 19, 2023

Describe the bug
On a french PC, when I press the 'a' key in a TextBox, that append 'a' to the text.
However, when I press Ctrl+a to Select All, that also add 'a' to the text.
When I check the KeyDown event to see why the hotkey do not work as expected, the Key contains Q, not A. Same for Ctrl+Z which is Ctrl+W in the hotkey check, etc...
(I press the physical 'A' key on my azerty keyboard)

If I want to select All, I have to type Ctrl+Q in browser at the moment.

@maxkatz6 I think this is why you cannot repro this issue in my other ticket. You probably are on a english PC with querty keyword.
image

This is probably due to to the Browser (see Additional context below), do you think I have to handle that in my code (with convertion table), of can you do something in Avalonia?

  • OS: Windows 10, Edge browser, french PC
  • Version 11 preview 6

Additional context
On collegue that worked with angular told me that when he receive key event, if he press Ctrl+a:
event.code => Key.Q
event.value => 'a'
so he had to check the control modifier and event.value for the hotkey...
and ctrl+shift+a => event.value is 'A' (uppercase when shift is also pressed), but event.code is still Key.Q.

@dbriard dbriard added the bug label Apr 19, 2023
@dbriard
Copy link
Contributor Author

dbriard commented Jun 6, 2023

Hi @maxkatz6 , I am wondering if you have seen this bug report and if it could be fixed for v11?
It is really anoying and should be fixed at Avalonia level IMO. I think it require some kind of querty to azerty remap table when running in browser. See additional context above.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant