-
Notifications
You must be signed in to change notification settings - Fork 728
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
fix(wasm): key tracking when no one is subscribing to Key<Down|Up> #18702
base: master
Are you sure you want to change the base?
fix(wasm): key tracking when no one is subscribing to Key<Down|Up> #18702
Conversation
This affects NavigationView (as reported in the original issue) because, for some reason, NavigationView's logic is written so that if any modifiers are pressed, it should not open the picker popup. |
f2f751b
to
542a226
Compare
#if __WASM__ | ||
#pragma warning disable IDE0051 // Remove unused private members | ||
[JSExport] | ||
private static void UpdateKeyStateNative(string key, bool down) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a manual test that explains what to test? Thanks!
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-18702/index.html |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-18702/index.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will need to improve keyboard state tracking in general as it is not completely reliable, e.g. when key is pressed before the window gets focused, opened #18714 to track this.
@MartinZikmund Actually, this is still the case on WASM after this PR. This only fixes missing tracking updates when KeyDown/Up has no listeners, but an out-of-focus press will still mess up the tracking. We will need to investigate that separately. |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-18702/index.html |
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-18702/index.html |
GitHub Issue (If applicable): closes #18617
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.Other information
Internal Issue (If applicable):