You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of React, ReactDOM/React Native, Redux, and React Redux are you using?
React: 18.1.0
ReactDOM/React Native: 18.1.0
Redux: 4.2.0
React Redux: 8.0.1
What is the current behavior?
After calling window.open() in a callback, useSelector in component isn't receiving updates from store any more, even though values in store are changed.
This only happens in Firefox and using "createRoot" from "react-dom/client" (in Chrome/Edge everything works ok).
I'm pretty sure this has to do with your build setup in some way. I've tried this with some other code examples and window.open doesn't block further dispatches in Firefox.
Just for a bit more info, this is reproducible on firefox in that build setup with plain setState, with redux completely stripped out. Seems unrelated to redux or react-redux
Thanks, it didn't occur to me trying to remove redux from the equation.
After more research I eventually found a probably related problem reported in react facebook/react#24458, which was fixed just a few days ago in react's main branch.
I tried my testcase with react@next and it seems to also fix this problem with firefox.
What version of React, ReactDOM/React Native, Redux, and React Redux are you using?
What is the current behavior?
After calling window.open() in a callback, useSelector in component isn't receiving updates from store any more, even though values in store are changed.
This only happens in Firefox and using "createRoot" from "react-dom/client" (in Chrome/Edge everything works ok).
https://codesandbox.io/s/nifty-mendel-5ucdij
What is the expected behavior?
Component keeps updating from store even after calling window.open();
Which browser and OS are affected by this issue?
Firefox 100.0.1, Windows 10
Did this work in previous versions of React Redux?
The text was updated successfully, but these errors were encountered: