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
Actual:
It moves to a wrong position, potentially outside of the viewport.
Expected:
It does not move away from the mouse
Root cause:
The layout of the app produces scrollbars on the parent element of the popup and focusing and moving it causes issues with calculations when those elements are scrolled. In Blazor there is a limit on how far up the DOM you can render popup elements and so you cannot fully take into account all possible CSS and scrolling settings.
You can read more about this here: https://docs.telerik.com/blazor-ui/knowledge-base/common-popup-causes-scroll-on-show and the fix would be similar to one proposed in the linked sample project - ensure that scrollbars are in the content, below the TelerikRootComponent and higher level elements have height:100% and overflow:hidden. In this app, the fix is not that trivial because it has a little more complex layout, responsive layout and a header, however.
Repro:
Actual:
It moves to a wrong position, potentially outside of the viewport.
Expected:
It does not move away from the mouse
Root cause:
The layout of the app produces scrollbars on the parent element of the popup and focusing and moving it causes issues with calculations when those elements are scrolled. In Blazor there is a limit on how far up the DOM you can render popup elements and so you cannot fully take into account all possible CSS and scrolling settings.
You can read more about this here: https://docs.telerik.com/blazor-ui/knowledge-base/common-popup-causes-scroll-on-show and the fix would be similar to one proposed in the linked sample project - ensure that scrollbars are in the content, below the
TelerikRootComponent
and higher level elements haveheight:100%
andoverflow:hidden
. In this app, the fix is not that trivial because it has a little more complex layout, responsive layout and a header, however.Also related and similar in root cause to #104
The text was updated successfully, but these errors were encountered: