-
Notifications
You must be signed in to change notification settings - Fork 392
fix: [M3-8124] - RegionSelect unexpected keyboard behavior
#10495
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: [M3-8124] - RegionSelect unexpected keyboard behavior
#10495
Conversation
| onKeyDown={(e) => { | ||
| if (e.key !== 'Tab') { | ||
| setSelectedRegion(null); | ||
| handleRegionChange(null); | ||
| } | ||
| }} |
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.
I'm curious about the original intention of this. Might warrant further discussion
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.
If i remember well i had this in place cause a tab keydown would clear the select, but that's not something i can reproduce at all, so i am frankly doubting my sanity doing something like this - should've commented why.
Long story short, thx for fixing
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.
No worries! 🚀
|
Coverage Report: ✅ |
abailly-akamai
left a comment
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.
This is much better, thx for fixing
Description 📝
Removes one-off
onKeyDownlogic from theRegionSelectto fix unexpected keyboard behavior ⌨️Behavior Before this PR ❌
Behavior After this PR ✅
How to test 🧪
As an Author I have considered 🤔