You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Android, when you start an interactive keyboard dismissal but then "abort" it by dragging the keyboard back up, the keyboard remains open but events emitted from the library make it seem as if its closed.
More specifically, when the interactive dismissal starts, the following event is emitted (which makes sense):
For reference on iOS, no events are emitted when the interactive dismissal starts and the following are emitted when it aborts, which leaves it correctly in an open state:
Describe the bug
On Android, when you start an interactive keyboard dismissal but then "abort" it by dragging the keyboard back up, the keyboard remains open but events emitted from the library make it seem as if its closed.
More specifically, when the interactive dismissal starts, the following event is emitted (which makes sense):
However when the dismissal is aborted, a
keyboardDidHideevent is emitted so the keyboard appears to be closed even though it's still open.For reference on iOS, no events are emitted when the interactive dismissal starts and the following are emitted when it aborts, which leaves it correctly in an open state:
Repo for reproducing
I'm re-using the repo used for a separate issue as it covers both cases.
https://github.com/iankberry/ios-interactive-keyboard-repro
To Reproduce
Expected behavior
The sticky view should remain above the keyboard while it is visible.
Screenshots
Screen.Recording.2025-12-10.at.11.30.26.AM.mov
Smartphone (please complete the following information):