What title says, we had to revert clickable to tapGestureFilters and other filters instead of using detectTapGestures because click wasn't fired sometimes under certain circumstances. More context:
After we migrated clickable to detectTapGestures, we were missing clicks on the buttons.
Symptoms: tap with regular speed, after click is up (lifted) sometimes ripple animates to pressed state and stays there and onClick is not fired. Reproducible not on every click and not for everyone.
Notable discoveries throughout exploration/revert:
It was reproducible only on emulators. All attempts to repro this on the
It was flaky, meaning that not everyone was able to reproduce it.
2.1 We were able to reproduce it on some linux machines that operates with mouse
2.2 We were able to reproduce it on the macs when you TAP on the trackpad. Not reproducible when you click.
Revert to tapGestureFilter fully solves the issue.
Seems like a timing/race issue when delay between down and up is very low, or smth along this lines.
It's an important issue to allow us to continue to migrate production code to suspend pointer to solve, hence p1.
Description
What title says, we had to revert clickable to tapGestureFilters and other filters instead of using
detectTapGesturesbecause click wasn't fired sometimes under certain circumstances. More context:After we migrated clickable to detectTapGestures, we were missing clicks on the buttons.
Symptoms: tap with regular speed, after click is up (lifted) sometimes ripple animates to pressed state and stays there and onClick is not fired. Reproducible not on every click and not for everyone.
Notable discoveries throughout exploration/revert:
tapGestureFilterfully solves the issue.Seems like a timing/race issue when delay between down and up is very low, or smth along this lines.
It's an important issue to allow us to continue to migrate production code to suspend pointer to solve, hence p1.