Skip to content

fix: collections in react canary & next 16 app router#10323

Open
nwidynski wants to merge 3 commits into
adobe:mainfrom
nwidynski:fix-issue-10298
Open

fix: collections in react canary & next 16 app router#10323
nwidynski wants to merge 3 commits into
adobe:mainfrom
nwidynski:fix-issue-10298

Conversation

@nwidynski

Copy link
Copy Markdown
Contributor

Closes #10298

✅ Pull Request Checklist:

  • Included link to corresponding React Spectrum GitHub Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exists for this component).
  • Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

@nwidynski

nwidynski commented Jul 13, 2026

Copy link
Copy Markdown
Contributor Author

@LFDanLu Next 16 app router uses React Canary, which is why this wasn't replicable in test. The bug itself was due to react/react#35091, which is landing in React 19.3+. Lmk what you think about this approach.

@nwidynski nwidynski changed the title fix: react activity in react canary & next 16 fix: collections in react canary & next 16 app router Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Collection components lose all items when re-shown by <Activity> after having been visible (return-visit case, not covered by #9300)

1 participant