Open asafkorem opened 2 years ago
@asafkorem is the todo column the right place for this? Could be backlog or bugathon it instead, as it is not urgent?
BTW: One work-around for this is to either apply the tap twice (conditionally, if iOS
), or preempt the actual tap with some senseless tap on a dead-space area on the screen (e.g. tap()
with specific coordinates), just for dismissing the keyboard.
@d4vidi I agree, backlog or bugathon fits better here.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe the issue is still relevant, please test on the latest Detox and report back.
Thank you for your contributions!
For more information on bots in this reporsitory, read this discussion.
The issue has been closed for inactivity.
@asafkorem do you know how to get this fixed? Could we sum the steps up for contributors?
According to internal issue
replaceText
doesn't suffer from this problem
What happened?
When using the keyboard (on a text field for example), tapping on visible elements outside the keyboard only dismisses the keyboard (but not handled as regular taps, as it should). That happens on Detox test but not on a manual test.
What was the expected behaviour?
The keyboard is being dismissed and the tap is handled regularly
Was it tested on latest Detox?