-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[Portal] Fix disablePortal not working #15701
Conversation
Details of bundle changes.Comparing: 014a07f...4fc3681
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice if we could include a test that would've failed without this fix.
I have added a failing test case, removed the class api, make the test strict mode ready and remove the outdated portal mock. This needed some proper clean up :). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very clean test. Just the disablePortal behavior needs a better description.
Thanks, I have removed the disablePortal
test suite. I think that it was redundant.
@@ -16,8 +16,7 @@ describe('<Popper />', () => { | |||
}; | |||
|
|||
before(() => { | |||
// StrictModeViolation: uses Portal | |||
mount = createMount({ strict: false }); | |||
mount = createMount({ strict: true }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Applies the change shown here to fix issue #15612
Closes #15612.