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 rendering of a Modal component (e.g. Toast or MessageBox) the position of the component is not fixed, which makes it look like the component flickers into the screen.
This behaviour does not always occur but is easily reproducible by opening a Modal multiple times and changing the width of the screen between render.
Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.
Hi Colleagues,
this issue is basically the same as described in this issue. So, please feel free to close this one as duplicate.
It seems that the issue affects all popup components extending the Popup class that are conditionally rendered.
Our Modals provider, conditionally renders the respective component with open="true" as default value, so developers can open popups without having to create a dedicated component for each popup. You can find out more about this in our Storybook.
In case you need a reproducible example without our Modals class, our wrapper or React, please let me know.
Describe the bug
On rendering of a Modal component (e.g. Toast or MessageBox) the position of the component is not fixed, which makes it look like the component flickers into the screen.
This behaviour does not always occur but is easily reproducible by opening a Modal multiple times and changing the width of the screen between render.
Isolated Example
https://stackblitz.com/edit/github-d34zwy?file=src%2FApp.tsx
Reproduction steps
Expected Behaviour
Ideally the Component should be rendered at the correct position without a change position being noticeable by a human.
Screenshots or Videos
No response
UI5 Web Components for React Version
2.4.0
UI5 Web Components Version
2.4.0
Browser
Chrome
Operating System
No response
Additional Context
No response
Relevant log output
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: