[0.88] Hide misplaced iOS 26 scroll edge effects on inverted lists
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ios, react-native
- Domain
- mobile
Research direction
Start by reviewing PR #58684 and commit 3b8f1f8, then inspect the iOS changes in RCTEnhancedScrollView and RCTScrollViewComponentView. Cherry-pick the commit onto the 0.88 stable branch and check that inverted lists no longer show misplaced edge effects, including with Reduce Transparency enabled and when the keyboard opens.
Written by the indexing model from the issue text.
Description
Target Branch
0.88
Link to commit or PR to be picked
https://github.com/facebook/react-native/pull/58684 (https://github.com/facebook/react-native/commit/3b8f1f822532af57d3eb61983ffc788465b3f72d)
Description
Target Branch
0.88
Link to commit or PR to be picked
https://github.com/facebook/react-native/pull/58684 (https://github.com/facebook/react-native/commit/3b8f1f822532af57d3eb61983ffc788465b3f72d)
Description
#58684 merged to main on Oct 2, after 0.88 branched, so 0.88.0 and 0.88.1 still render the misplaced edge effects on inverted ScrollViews.
On iOS 27 it's worse than the dimming described in the PR. With Reduce Transparency on, the effect is an opaque fill, and once an inverted list resizes (e.g. the keyboard opens) it can cover the whole list. Users see a blank chat conversation. We had 18 user reports in production the week iOS 27 shipped.
The commit cherry-picks cleanly onto 0.88-stable. The change is iOS only, in RCTEnhancedScrollView and RCTScrollViewComponentView.
- Dominant language
- JavaScript
- Stars
- 429
- Forks
- 11
- Avg merge
- 4h 13m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from reactwg/react-native-releases
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
reactwg/react-native-releases#1491 ·
-
Type Pick Request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
reactwg/react-native-releases#1472 · 1 comment ·
-
Type Pick Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
reactwg/react-native-releases#1435 · 1 comment ·
-
Type Pick Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
reactwg/react-native-releases#1427 · 1 comment ·
-
Type Pick Request
Difficulty 1/5 Under an hour Newbie friendliness 78/100
reactwg/react-native-releases#1349 · 1 comment · 1 reaction ·
All issues in reactwg/react-native-releases
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
check:failed logos:add
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
iptv-org/database#38874 · 1 comment ·
Maintainers usually reply within 4 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#5193 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100