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
On some Chrome browsers, when using portalElement, the tab crashes when opening the popover.
The popover does open for a few seconds before the tab crashes, as if there was some kind of infinite loop.
There is nothing in the console before the crash.
It's still unclear which browsers are impacted: for the same version, some people can replicate the crash, but not everyone -› there is an unknown external factor.
One of the Chrome versions impacted: Version 120.0.6099.109 (Official Build) (arm64)
We were initially on version 0.2.16 but we can also replicate it with the latest version.
That's probably related to the following line which we should address properly in a near future. Both getRootElement and portalElement are returning the document.body which is probably the cause for the loop in this case.
Current behavior
Hello :)
On some Chrome browsers, when using
portalElement
, the tab crashes when opening the popover.The popover does open for a few seconds before the tab crashes, as if there was some kind of infinite loop.
There is nothing in the console before the crash.
It's still unclear which browsers are impacted: for the same version, some people can replicate the crash, but not everyone -› there is an unknown external factor.
One of the Chrome versions impacted:
Version 120.0.6099.109 (Official Build) (arm64)
We were initially on version
0.2.16
but we can also replicate it with the latest version.On a team of 4 ( on mac )
Minimal reproduction step:
https://stackblitz.com/edit/vitejs-vite-dmafri?file=package.json,src%2FApp.tsx&terminal=dev
And thank you for the hard-work, we truly love using ariakit ❤️
Steps to reproduce the bug
This should be enough to reproduce it:
Expected behavior
no crashes
Workaround
We've used react's
createPortal
insteadPossible solutions
No response
The text was updated successfully, but these errors were encountered: