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
Initially the Tooltip shows up positioned in such way that most of its content not visible. If you close the Tooltip and click the "Click me" text to show it again, it is shown over the whole page.
Expected/desired behavior
The positioning on first opening is incorrect. The Tooltip should be positioned identically in both cases (when opened for the first time, and on subsequent opening).
Environment
Kendo UI version: 2020.3.1021
jQuery version: x.y
Browser: [all]
The text was updated successfully, but these errors were encountered:
@joneff
The attached website basically contains two Html pages, one with the Tooltip and the other is the content loaded in the Tooltip. So the scenario is isolated as much as possible. The issue is not reproducible in the dojo, because in that case the content will have to be loaded from another domain and this makes the Tooltip render it in an iframe. The issue is not exhibited when an iframe is rendered, i.e. the content must be loaded from the same domain, to avoid it being placed in an iframe, thus I've attached a website with a test page and a content page.
Dimitar-Goshev
changed the title
Tooltip inconsistent positioning when large content is loaded
Inconsistent Tooltip positioning when large content is loaded
Feb 23, 2021
Bug report
WebSite12.zip
Reproduction of the problem
A sample WebSite is attached.
Current behavior
Initially the Tooltip shows up positioned in such way that most of its content not visible. If you close the Tooltip and click the "Click me" text to show it again, it is shown over the whole page.
Expected/desired behavior
The positioning on first opening is incorrect. The Tooltip should be positioned identically in both cases (when opened for the first time, and on subsequent opening).
Environment
The text was updated successfully, but these errors were encountered: