Skip to content

Commit a72fbc1

Browse files
docs(common): wrong popup position - special troubleshooting section
1 parent bdf9c0a commit a72fbc1

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

troubleshooting/general-issues.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ position: 1
1212

1313
This page provides solutions for common issues you may encounter while working with Telerik UI for Blazor components.
1414

15+
* [Popups Do Not Work](#popups-do-not-work)
16+
* [Wrong Popup Position](#wrong-popup-position)
17+
1518
## Popups Do Not Work
1619

1720
There are three common reasons for this
@@ -38,6 +41,24 @@ app {
3841
````
3942

4043

44+
## Wrong Popup Position
45+
46+
The position of popups (Window, various dropdowns such as DropDownList, ComboBox, DatePicker) can be wrong or offset.
47+
48+
The most common reason for such a problem is that the [`<TelerikRootComponent>`]({%slug getting-started/what-you-need%}#project-configuration) does not match the `<body>` and the browser viewport - this is required because that component is the topmost element our components can access in order to render popups/dropdowns.
49+
50+
There are several common cases when such a mismatch occurs:
51+
52+
* The position and size of the `<app>` element (or however the root component of your Blazor app is called) does not match the `<body>`.
53+
54+
* There are CSS rules that offset the `<app>` element or its parent element (such as `position: absolute` or `margin: auto`, or placing it in some form of popup like a jQuery dialog).
55+
56+
* There are CSS rules that alter the positioning of an element or class used in the Telerik popup elements.
57+
58+
* There is more than one `<TelerikRootComponent>` in the app (for example, a certain Razor Component has its own) - there should be only one instance in the main layout.
59+
60+
You can check the application for such issues and ensure that the `<app>` element size and position matches the `<body>` and the browser viewport, and that the `<TelerikRootComponent>` is a direct child of the `<app>` element and encompasses the `@Body` in the main layout.
61+
4162
## See Also
4263

4364
* [JavaScript Errors Troubleshooting]({%slug troubleshooting-js-errors%})

0 commit comments

Comments
 (0)