Bug: Multiple React.Suspense breaks if all not wrapped in <Suspense> about react

[acdlite]

I would expect the Without Suspense section to be empty

React will not skip over content unless you give it an explicit fallback. It will block ("suspend") the update instead. So what you're seeing is actually the intended behavior.

If you want it to show empty until it finishes loading, the solution is to use a Suspense boundary with null as the fallback.

[markwylde]

Thanks @acdlite for your time :)

But surely it should only effect it's own tree? In the example they are both empty.

Is it because of a missing <Suspense> in the parent? Are we saying that if a component has the potential to Suspend (ie, return a promise) then it is required to have a Suspense in the parent somewhere?. If so, should this throw a React error or warning in the console, if it's missing?

[markwylde-deriv]

@acdlite is it documented anywhere? How components that throw suspense will cause side effects in other trees?

I'm probably just missing it, but I couldn't see anything here:
https://react.dev/reference/react/Suspense