-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Standardize on one method for detecting keyboard state #13582
Comments
Triggered auto assignment to @flaviadefaria ( |
Sorry @flaviadefaria, this is not a bug, just a cleanup issue, so I am removing your assignement. |
All right, here is what I found out. Virtual keyboard exports two methods:
So, I think that all of this can be refactored to just use the two HOCs we currently have for |
Hm, I'm not sure why GH didn't link the PR with this issue #13629 but this was deployed to production, so I'm going to close this. |
@thesahindia can you please accept the job and reply here once you have? |
Accepted, thanks! |
Paid @thesahindia , closing cuz this shouldn't need regression test steps |
Problem
There are two ways for components to detect the keyboard state:
withKeyboardState
- this works on native devices, but doesn't have support for mobile webVirtualKeyboard.shouldAssumeIsOpen()
- this appears to work on both native devices and mobile web. Originally added in this PR.Neither option is used consistently, leading to inconsistent behavior in the app.
Solution
VirtualKeyboard
works for mobile webVirtualKeyboard
intowithKeyboardState
withKeyboardState
everywhereVirtualKeyboard
CC @jasperhuangg @parasharrajat
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: