Stale IntersectionObserver entries abort callbacks for active observers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.3k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 4
Description
Description
The IntersectionObserver manager explicitly tolerates stale native entries when an observer is disconnected between commit and mount. However, encountering one missing registration returns from the entire notification pass, dropping every later entry and callback in the same native batch, including entries for still-active observers.
Expected behavior
A stale entry for a disconnected observer should be ignored while notification continues for all active observers in the batch, matching the equivalent ResizeObserver handling.
React Native Version
0.87.1 and current main
Affected Platforms
New Architecture - All
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 at the IntersectionObserver manager's notification pass and compare its stale-entry handling with the equivalent ResizeObserver handling mentioned in the issue. Reproduce or inspect a batch containing a disconnected observer followed by active observers, then verify that stale entries are ignored and later active callbacks still run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100