Gesture doesn't recognize in the view's spanned region on all the platforms
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 296
Description
### Description
We have a custom grid view where we arrange two rows, one at the top and one at the bottom of the grid. Each row contains two custom border controls positioned on the left and right sides.
For the spanning use case, we expand the first row’s second child so that it occupies the bottom region of the second row. We then hide the second row’s second child, allowing the first row’s second child to fully cover that area. The layout works correctly.
However, I am facing an issue with gesture interactions in the spanned region of the child view. I am unable to detect tap interactions in the area where the view is spanned.
Please review this request and assist as soon as possible.
https://github.com/user-attachments/assets/80a2fdb4-b5fb-4e3f-9c82-45c63f5f9c3f
### Steps to Reproduce
1. Run the attached sample
2. Tap first row's second child's spanned area.
3. You can reproduce the reported issue.
[GestureIssue.zip](https://github.com/user-attachments/files/25436386/GestureIssue.zip)
### Link to public reproduction project repository
_No response_
### Version with bug
10.0.40
### Is this a regression from previous behavior?
No, this is something new, Not sure, did not test other versions
### Last version that worked well
Unknown/Other
### Affected platforms
iOS, Android, Windows, macOS
### Affected platform versions
All the platforms
### Did you find any workaround?
No
### Relevant log output
```shell
```
Contributor guide
Research direction
Start by running the attached GestureIssue.zip sample and reproduce the issue by tapping the first row's second child's spanned area. Compare gesture behavior across iOS, Android, Windows, and macOS; done means taps are detected in the spanned region on the affected platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100