software-mansion / software-mansion/react-native-screens
[Android] headerLeft and headerRight remain touchable while native search bar open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 713
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 71
Description
Description
When displaying a native search bar on Android, any touchables in the headerLeft or headerRight remain touchable when the search bar is focused. This occurs in both Fabric and Paper.
https://github.com/user-attachments/assets/6ac012e4-1d8b-4b83-85a4-6116d1e05438
There is a similar situation here regarding the visibility of these elements that was resolved a while ago. I'm not sure if this existed then as well.
Steps to reproduce
I originally found this in an Expo project, but I forked this repo and replicated the bug in the Example project to simplify the environment.
- Clone https://github.com/sept-jm/react-native-screens
- Build and open the Example/FabricExample project on Android
- Go to "Search bar"
- Click the magnifying glass
- Tap where the "Some" button used to be visible
- See the onClick event in the toast
Snack or a link to a repository
https://github.com/sept-jm/react-native-screens
Screens version
4.19.0
React Native version
0.81
Platforms
Android
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
Android emulator
Device model
No response
Acknowledgements
Yes
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Search bar screen in the Example/FabricExample project and trace how Android handles touches for headerLeft and headerRight while the native search bar is focused. Reproduce the issue on Android in both Fabric and Paper, then verify that tapping where those controls were displayed no longer triggers their actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100