Release high-priority list updates after no-op commits #59295

Open
javache opened 8:10am on October 21, 2026 wants to merge 79 Ξ” into facebook/react-native main from
export-D126635244

Pull Request Overview

  • Opened on October 21, 2026
  • Status Open
  • Commit count 2 with first commit October 16, 2026

Total Delta

79 Total Diff Delta

Open Days

Open 15 weekdays

Test Delta

0 Diff Delta in Test Files
Breakdown by Phase

How long has this pull request spent in each phase of its lifecycle?

Fraction of total time Business days Phase
 
2.8 days Authoring 2 commits before pull request opened for review
 
0.0 days Awaiting first review
 
15.9 days Revising work with 0 commits in response to 0 reviews that left 1 comment

Total time for pull request still awaiting merge (longer than repo's target): 18.7 business days

Author avatar

Release high-priority list updates after no-op commits

Summary:
VirtualizedList can leave its high-priority update flag set when a queued cells updater becomes a no-op, because componentDidUpdate does not run. Complete the high-priority attempt using a setState callback so the next urgent window update does not wait for the batching timer.

Scope completion to its attempt so an older callback cannot clear newer work scheduled during componentDidUpdate or onEndReached. Preserve the no-op fast path and the existing once-per-commit scheduling protection.

Changelog:
[General][Fixed] - Avoid delaying urgent VirtualizedList rendering after queued no-op updates

Differential Revision: D126635244

Comments Threads Pending Resolution

Resolved Comment Threads

No resolved comments have been left on this PR.