-
Notifications
You must be signed in to change notification settings - Fork 49.3k
Handle legacy root contains in clearContainer #18781
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
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 4ba1b2f:
|
Btw don't forget to update both files. |
Details of bundled changes.Comparing: 88d0be6...4ba1b2f react-dom
Size changes (stable) |
Details of bundled changes.Comparing: 88d0be6...4ba1b2f react-dom
Size changes (experimental) |
I've updated this PR with another possible fix. I'll leave this PR just to show the changes anyway, but there might be an alternative approach we might want to take instead. |
aa046af
to
fc25111
Compare
Fix Fix Fix Fix
This PR fixes the regression we're seeing internally. I think there might be a better place to check for this though. Let me post a potential alternate PR here shortly... Edit Potential alternate #18792 |
When debugging an internal issue, I noticed that we have an issue where we clear down a root that has existing content. This particular fix checks in
clearContainer
if the container we're trying to clear has a legacy container and if it does, checks to see if it matches the root we expected.