Unplanned
Last Updated: 17 Apr 2026 08:46 by Vitro
Created by: Vitro
Comments: 0
Category: Notification
Type: Bug Report
0

Bug report

Notifications overlap when multiple invoked on mobile. Tested on iPad Air 13 2025 v18.6 and iPhone 26.3.1

Regression with v.2023.1.314

Reproduction of the problem

https://demos.telerik.com/kendo-ui/notification/index

Click on "As a popup at bottom-right" multiple times

The notifications are overlapping and broken into multiple lines



Expected/desired behavior

Notifications should not overlap and rendering on a single line

Environment
Kendo UI version: 2026.1.415
Browser: [ ipadOS 17.1.1 Safari ]

Unplanned
Last Updated: 08 Feb 2024 13:28 by ADMIN
Created by: Gerard
Comments: 2
Category: Notification
Type: Feature Request
1

At present, popup notifications stay in one place on the screen and if you resize the browser while there is a visible notification, it will no longer be in the expected corner of the viewport (e.g., the bottom right) - they may be somewhere around the middle or outside of the visible viewport.

The following article shows how you can reposition them with your own by calculating the new position rules: https://docs.telerik.com/kendo-ui/controls/layout/notification/how-to/move-on-window-resize.

An alternative that may be simpler is to use your own container with fixed positioning and use inline notifications in it, instead of popup notifications. With this this, you can define such a fixed position on your div that satisfies the layout and the notifications will add content to it. An example is available in the following article: https://docs.telerik.com/kendo-ui/controls/layout/notification/how-to/move-on-notification-hide.

Ideally, this feature will be built-in behind a property that will have the notification attach a handler to window.resize and will reposition the popupts automatically, maybe with a configurable delay (that is, how often after resizing the code should run). Perhaps a property like "resizeRepositionTimeout: number" can be used for both - if unset, it will default to undefined and no repositioning will occur, if set to a number, it will be used to throttle the resize event.