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
This bug is a specific issue with Android only. iOS is working fine. It is specifically an issue with Androids TalkBack screen reader trying to read elements.
Environment info
Library
Version
@gorhom/bottom-sheet
4.6.3
react-native
0.74.1
react-native-reanimated
3.11.0
react-native-gesture-handler
2.16.2
Steps To Reproduce
Create a simple app. Can be one screen.
Setup a bottom sheet
Add a few elements in the bottom drawer. I suggest a element followed by a followed by another followed by .
Install the app into Android and turn on the TalkBack screen reader.
Try to highlight the elements
Describe what you expected to happen:
Expected: You should be able to highlight the elements individually and have it be read.
Actual: You can't highlight the elements. Instead, they are all read at once when you highlight the parent bottom sheet element. This is confusing if you have several headers or sections that should be read as you navigate though the bottom sheet.
Okay I figured it out. If you wrap the contents of the bottom sheet inside a it works just fine. I updated my snack to have both the original "broken" example and an updated working example. Hope this helps future people.
Bug
This bug is a specific issue with Android only. iOS is working fine. It is specifically an issue with Androids TalkBack screen reader trying to read elements.
Environment info
Steps To Reproduce
Describe what you expected to happen:
Expected: You should be able to highlight the elements individually and have it be read.
Actual: You can't highlight the elements. Instead, they are all read at once when you highlight the parent bottom sheet element. This is confusing if you have several headers or sections that should be read as you navigate though the bottom sheet.
Reproducible sample code
You can use this snack to reproduce the issue.
Here is me demoing the issue.
AndroidBottomSheetIssue.mp4
The text was updated successfully, but these errors were encountered: