-
Notifications
You must be signed in to change notification settings - Fork 47k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Nested useTransition makes isPending of outer one always false #26226
Comments
gaearon
added
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Type: Bug
Component: Concurrent Features
and removed
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
labels
Feb 24, 2023
gaearon
changed the title
Bug: nested useTransition makes isPending of outer one always false
Bug: Nested useTransition makes isPending of outer one always false
Feb 24, 2023
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Feb 25, 2023
…ansition Fixes facebook#26226. (Is this the right fix?)
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Feb 25, 2023
…ansition Fixes facebook#26226. (Is this the right fix?)
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Mar 16, 2023
…ansition Fixes facebook#26226. (Is this the right fix?)
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Mar 16, 2023
…ansition Fixes facebook#26226. (Is this the right fix?)
sophiebits
added a commit
to sophiebits/react
that referenced
this issue
Mar 16, 2023
…ansition Fixes facebook#26226. (Is this the right fix?)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nested
startTransition
call "takes over" and makes parentstartTransition
unable to trackisPending
.Seb says it's a bug.
Repro:
https://codesandbox.io/s/pensive-breeze-rg70wn?file=/IndexPage.js:192-288
isPending
inIndexPage.js
istrue
However,
isPending
inApp.js
isfalse
.Expected:
isPending
inApp.js
is alsotrue
.The text was updated successfully, but these errors were encountered: