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
{{ message }}
Repository navigation
rc-trigger cause popup window to glitch when there not enough width size #496
When the popup window do not have enough space it causes the popup to glitch. You can observe this behavior in the video linked below:
2024-12-02_16-19-16.mp4
Step to reproduce:
Navigate to the portal example in the demo using rc-trigger v2.2.5.
Resize the window so that the popup appears slightly off-screen.
Watch for the glitch in the popup during the transition. It looks like the style are being recalculate.
This is causing issue because when working with microfrontend, each microfrontend has it designed container. The glitch happens when the popup extends outside the container of the microfrontend that triggers it, leading to this unexpected behavior.
Reacted by Mike Ellis, John Feola, Allegra Weldon, Jon Cullison and Tielman
@zombieJ@afc163 Hi we are running into this really weird bug. Can you look into this? It didn't seem like this was a problem when using antd v4 which was using rc-trigger v5.3.4
changed the title [-]rc-trigger cause popup window to glitch when there not enough width size when using portal[/-][+]rc-trigger cause popup window to glitch when there not enough width size[/+]on Dec 5, 2024
Activity
yhy-1 commentedon Dec 2, 2024
@zombieJ @afc163 Hi we are running into this really weird bug. Can you look into this? It didn't seem like this was a problem when using antd v4 which was using rc-trigger v5.3.4
yhy-1 commentedon Dec 4, 2024
@MadCcc could someone look into this issue? This results in this behavior in the dropdown which makes it unuseable.
2024-12-04_14-41-26.mp4
[-]rc-trigger cause popup window to glitch when there not enough width size when using portal[/-][+]rc-trigger cause popup window to glitch when there not enough width size[/+]yhy-1 commentedon Jan 7, 2025
@zombieJ @afc163 @MadCcc could someone look into this issue?