Delay in rendering sub-collections with Suspense

[vezaynk]

Provide a general summary of the issue here

After upgrading to react-aria-components 1.2.2, I began encountering an issue with Combobox where nested collections aren't rendered immediately.

I have a component structure that looks like this, with the behavior as comments:

const Component = () => {
    <Popover>
       <Suspense>
           <SubComponent />
}

const SubComponent = () => {
  useSuspenseQuery()
  <Menu items={...}> //  <--- 1. This renders after Suspense query is done
   (section => 
       <MenuSection>
           <Header /> //  <--- 2. This appears at the same time as the Menu
           <Collection items={section.items}>
               <MenuItem /> // <--- 3. This appears after a short delay, after everything else

Instead, I would expect to see the full Menu, Header, MenuItems rendered as soon as the suspense query is resolved.

🤔 Expected Behavior?

Behavior on react-aria-components@1.2.1

Screen.Recording.2025-09-17.at.18.31.55.mov

😯 Current Behavior

Behavior on react-aria-components@1.2.1

Screen.Recording.2025-09-17.at.18.29.20.mov

💁 Possible Solution

No response

🔦 Context

No response

🖥️ Steps to Reproduce

https://codesandbox.io/p/sandbox/react-aria-combobox-bug-forked-q3khch

Version

react-aria-components@1.2.2

What browsers are you seeing the problem on?

Firefox, Chrome

If other, please specify.

No response

What operating system are you using?

MacOS

🧢 Your Company/Team

No response

🕷 Tracking Issue

No response

[LFDanLu]

Strange, I've tracked it down to the collection filtering PR but I'm not quite sure why those changes would cause this change in behavior. It also seems to have some dependency on the React version since it seems to work fine in React 19, but only with Strict Mode...

[vezaynk]

@LFDanLu Is a revert patch on it possible, or is it a breaking change? Right now I'm sandwiched between being unable to upgrade due to this bug but, but not being able to downgrade due to needed the fix for this #8822. Im going to try to apply the patch from #8835 to the last release in the meantime.

[vezaynk]

Actually Im confused. The collection filtering PR was part of the 1.2.1 release, no? The breakage this issue is about was introduced only to 1.2.2, and wasn't there in 1.2.1.

[LFDanLu]

Oh you are right my mistake, must have gotten my local env in some kinda of cached state. It seems to be due to something in #8835 which is part of the latest patch

[vezaynk]

Yes, that aligns with what I’m seeing. That PR both fixes one issue and introduces another for us. We’re exploring downgrading to 1.11.0 right now to try to escape it. A resolution to this would be highly appreciated!

…

On Thu, Sep 18, 2025, at 4:05 PM, Daniel Lu wrote: *LFDanLu* left a comment (adobe/react-spectrum#8885) <#8885 (comment)> Oh you are right my mistake, must have gotten my local env in some kinda of cached state. It seems to be due to something in #8835 <#8835> which is part of the latest patch — Reply to this email directly, view it on GitHub <#8885 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOHZOVLHKGQD6DELNYPQQT3TMGBVAVCNFSM6AAAAACGZX42LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBZGQ4DAOBXGQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[LFDanLu]

Just a heads up but we are aiming to release the fix for this in our next release, should be end of this month/early next month. If you'd like to test the fix before then, you can try the latest nightly.