[Android] position: absolute shouldn't be cut off within a container with border
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.3k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 4
Description
Description
If you have an element position: absolute with negative offset within a container with a border, it's going to be cut off, it's like overflow: hidden of the container is suddenly enabled by the border. But if you remove the border of the container, it works well. This issue only happens on Android.
#3198 is a similar issue, and was reported with lots of discussions. However, I believe they are not exactly the same.
Reproduction
I've made an example on rnplay to reproduce the issue.
Solution
TBD
Additional Information
- React Native version: 0.33 (rnplay), 0.39 (the version I currently use)
- Platform: Android
- Operating System: MacOS
Contributor guide
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 linked rnplay reproduction and compare its behavior with the related issue #3198. Investigate the Android-specific case of a bordered container and an absolutely positioned child with a negative offset; done means the child is no longer clipped in that reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100