-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[docs] Replace react-frame-component with concurrent safe impl #20677
Conversation
Details of bundle changes.Comparing: 76f5f91...14578ec Details of page changes
|
@eps1lon You are not going to like this:
From what I recall, we had this issue or a very similar one in the past with Firefox only. We solved it by injecting the styles inside the body instead of the head. |
That would be very suspicious to me. Right now it doesn't even work without injecting any styles. |
How do you decide when to use which? |
new: makeStyles, old: withStyles. Refactoring happens when you're already working on the code. |
Ah okay. But presumably this doesn’t apply to components because of things like |
Yeah. But all of these could be solved. It's just not necessarily worth it considering we want to switch to styled-components. I'm not looking forward to having wrappers all over the place again but that's a dev-tooling issue. |
react-frame-component
callsdocument.write
during render which isn't concurrent mode safe (see ryanseddon/react-frame-component#159). It's also unnecessary since they falsely assume portaling intodocument.body
is unsafe because it's unsafe forrender()
.createPortal()
andrender()
have different semantics.It also has a lot of logic that we no longer need as of . Since it seems to not be maintained anymore (months old unanswered issues/prs, testing on node 6 etc) we it's not clear if these issues get addressed.
Also switches from withStyles to makeStyles
Related to #13394