We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Application crashes on initialization when trying to create an Accelerator key for the go back/go forward keys!
A really annoying bug that has been around for ages. Is it really impossible to fix this?
#7720
Add a keyboard accelerator to any page:
<Page.KeyboardAccelerators> <KeyboardAccelerator Key="GoBack" Invoked="NavigateBack"/> </Page.KeyboardAccelerators>
Expected a simple keyboard accelerator to map to the GoBack / GoForward key on my Microsoft Natural Ergonomic Keyboard 4000 v1.0
No response
WinUI 3 - Windows App SDK 1.6.3: 1.6.241114003
Windows 11 (24H2): Build 26100
The text was updated successfully, but these errors were encountered:
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Application crashes on initialization when trying to create an Accelerator key for the go back/go forward keys!
A really annoying bug that has been around for ages. Is it really impossible to fix this?
#7720
Steps to reproduce the bug
Add a keyboard accelerator to any page:
Expected behavior
Expected a simple keyboard accelerator to map to the GoBack / GoForward key on my Microsoft Natural Ergonomic Keyboard 4000 v1.0
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.6.3: 1.6.241114003
Windows version
Windows 11 (24H2): Build 26100
Additional context
No response
The text was updated successfully, but these errors were encountered: