-
Notifications
You must be signed in to change notification settings - Fork 105
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
[Bug]: Seamless interaction issue on front page with alternating touch and keyboard inputs #621
Closed
1 task done
Labels
Comments
6 tasks
6 tasks
ProjectMuBot
pushed a commit
that referenced
this issue
Jan 21, 2025
## Description Fixes #621 Fix the bug in event handling that occurs when alternating between touch and keyboard inputs, ensuring seamless interaction. - [x] Impacts functionality? - [ ] Impacts security? - [ ] Breaking change? - [ ] Includes tests? - [ ] Includes documentation? - [x] Backport to release branch? ## How This Was Tested Tested on Surface Laptop and Surface Pro. Booted to UEFI front page and alternated between Touchpad and Keyboard for operation. The interaction was seamless. ## Integration Instructions N/A --------- Co-authored-by: Wenbo Hou <wenbhou@microsoft.com>
makubacki
pushed a commit
to makubacki/mu_plus
that referenced
this issue
Jan 22, 2025
## Description Fixes microsoft#621 Fix the bug in event handling that occurs when alternating between touch and keyboard inputs, ensuring seamless interaction. - [x] Impacts functionality? - [ ] Impacts security? - [ ] Breaking change? - [ ] Includes tests? - [ ] Includes documentation? - [x] Backport to release branch? ## How This Was Tested Tested on Surface Laptop and Surface Pro. Booted to UEFI front page and alternated between Touchpad and Keyboard for operation. The interaction was seamless. ## Integration Instructions N/A --------- Co-authored-by: Wenbo Hou <wenbhou@microsoft.com>
6 tasks
makubacki
added a commit
that referenced
this issue
Jan 22, 2025
…623) ## Description Cherry-pick from release/202405 backported to release/202311. --- Fixes #621 Fix the bug in event handling that occurs when alternating between touch and keyboard inputs, ensuring seamless interaction. - [x] Impacts functionality? - [ ] Impacts security? - [ ] Breaking change? - [ ] Includes tests? - [ ] Includes documentation? - [x] Backport to release branch? ## How This Was Tested Tested on Surface Laptop and Surface Pro. Booted to UEFI front page and alternated between Touchpad and Keyboard for operation. The interaction was seamless. ## Integration Instructions N/A
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
When operating on the front page, switching between touch and keyboard inputs does not result in a seamless interaction. This issue has been observed on both Surface Laptop and Surface Pro devices. The problem occurs when users alternate between using the touchpad and keyboard, leading to inconsistent behavior and a disrupted user experience.
Expected Behavior
When operating on the front page, switching between touch and keyboard inputs should result in a smooth and consistent interaction. Users should be able to alternate between using the touchpad and keyboard without experiencing any interruptions or inconsistent behavior. The transition between inputs should be seamless, providing a fluid and uninterrupted user experience.
Steps To Reproduce
Reproduce Procedure:
1.Reboot DUT and press Vol+ to boot into UEFI UI
2.Try to use arrow key to change tabs in left panel, find it works.
3.Use touchpad to operate system:
a). Select PC Information tab
b). Click SN in the right panel and then click OK button.
c). Select Device tab(any tab in left panel)
4. Try to use arrow key in blade to change tabs in left panel, observe: it not works.
Expected results:
Arrow key in blade always can be used to change tabs in left panel
Actual results:
Arrow key in blade can not change tabs in left panel
Build Environment
Version Information
Urgency
Low
Are you going to fix this?
I will fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
The text was updated successfully, but these errors were encountered: