-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
fix(Popup): default open position #3029
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3029 +/- ##
==========================================
+ Coverage 99.89% 99.89% +<.01%
==========================================
Files 170 170
Lines 2809 2818 +9
==========================================
+ Hits 2806 2815 +9
Misses 3 3
Continue to review full report at Codecov.
|
@levithomason Seems that it's really an bug in ReactDOM, it tried to debug this. The issue comes from the The simpliest and stupid solution, disable html preview for specific examples. However, I'm not sure, that it's the best solution. |
…to fix/pop-open-position
…to fix/pop-open-position # Conflicts: # package.json # yarn.lock
….com/Semantic-Org/Semantic-UI-React into fix/pop-open-position # Conflicts: # docs/src/components/ComponentDoc/ComponentControls/ComponentControls.js # docs/src/components/ComponentDoc/ComponentExample/ComponentExample.js
….com/Semantic-Org/Semantic-UI-React into fix/pop-open-position # Conflicts: # yarn.lock
Released in |
Fixes #2991.
This PR was branched from #3020 to perform some cleanup and updates since the original PR was from a fork's master and couldn't be updated.
I've also added a "Default Open" example to the docs for this use case.
It seems there is a bug with the use of
ReactDOM.createPortal
inInnerPortal
. When rendering a Portal withopen
set to true on first render, an infinite loop is entered upon rendering theInnerPortal
. IfcreatePortal
is bypassed, there is no infinite loop. I do not yet know why this is :/