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
{{ message }}
This repository was archived by the owner on Jul 9, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 9, 2026. It is now read-only.
[RichText] if keyboard is up and another RichText is tapped into, keyboard is dismissed #291
changed the title [-]If keyboard is up and another RichText is tapped into, keyboard is dismissed[/-][+][RichText] if keyboard is up and another RichText is tapped into, keyboard is dismissed[/+]on Nov 28, 2018
I have a theory for this one: since the message between native and RN is asynchronous (it is, right?), when you tap on the second rich text filed, android does what it's supposed to and switches focus. Then the onBlur gets dispatched and RN asks the first field to blur itself. This doesn't check if the receiver is focused or not and asks to hide the keyboard anyway.
Activity
[-]If keyboard is up and another RichText is tapped into, keyboard is dismissed[/-][+][RichText] if keyboard is up and another RichText is tapped into, keyboard is dismissed[/+]koke commentedon Nov 29, 2018
I have a theory for this one: since the message between native and RN is asynchronous (it is, right?), when you tap on the second rich text filed, android does what it's supposed to and switches focus. Then the onBlur gets dispatched and RN asks the first field to blur itself. This doesn't check if the receiver is focused or not and asks to hide the keyboard anyway.
daniloercoli commentedon Nov 29, 2018
Reopening this issue since i can still reproduce the problem.
daniloercoli commentedon Nov 29, 2018
Made a short video where the keyboard is dismissed tapping on a RichText component: https://cloudup.com/cwhQI2NUhcT
The issue happened twice or 3 times in the video. The one at the end is easy noticeable.
mzorz commentedon Nov 29, 2018
Effectively closed in #296