Last Updated: 10 Oct 2023 13:08 by ADMIN

The Notification is not entirely displayed when Default or Classic themes are selected and scroller appears on the page.

To reproduce
Steps to reproduce the behavior:

  1. Open the demos -
  2. Click on the 'As a popup at bottom-right' button.

Expected behavior
The Notification seems to be cut at the end.


With versions prior 6.4.0, the Notification was displayed with a slight distance on the right


Affected package (please remove the unneeded items)

  • theme-default
  • theme-classic

Affected suites (please remove the unneeded items)

  • Kendo UI for jQuery

Affected browsers (please remove the unneeded items)

  • All
Last Updated: 20 Oct 2022 11:22 by ADMIN
Release R1.2023-Increment.1(09.Nov.2022)

Bug report

When there is "appendTo" in the Notification, the hide event fires multiple times.

Reproduction of the problem

  1. Open this dojo example and observe the console.

Current behavior

There are too many fired hide events for notifications. More than one event for every notification

Expected/desired behavior

Hide event should be fired single time per Notification.


To see how should it work, here is the sample dojo example.


  • Kendo UI version: 2022.3.913
  • Browser: [all]
Last Updated: 19 May 2021 08:36 by ADMIN
Created by: Anna
Comments: 1
Category: Notification
Type: Bug Report

I'm testing with the NVDA screen reader.

1. Notifications are not announced by the screen reader, violating success Criterion 4.1.3.

2. Notifications are not accessible by keyboard.

3. The "close" button is not semantically a button.

4. The "close" button is not focusable by keyboard.

5. Auto-hiding notifications violate the 2.2 guideline (enough time). I can give my user an option to see notifications for a longer time, say 100 seconds instead of 10, but unable to close them by keyboard, they can end up with an overflow of messages.

6. The color contrasts are insufficient (4.26 for the red ones, only 2.73 for the green ones).

Notifications are listed on as AA-level compliant, and while I understand they're one of the hardest component to make accessible due to their asynchronous nature, the current implementation is closer to a bad practices example than a correct solution.

Last Updated: 25 Feb 2020 14:20 by ADMIN
Created by: Anna
Comments: 1
Category: Notification
Type: Bug Report


Run dojo at

Current behavior

All three notifications are removed after one second

Expected behavior

The blue notification should be removed after 2 seconds, the orange one after 1 second, the red one never.


The bug only occurs with the appendTo option.

In the showStatic method, we clearly see all displayed notifications are iterated over and being attached the _hideStatic method. In my example:

  1. the blue notification is shown and scheduled to be hidden after 2s
  2. the red notification is shown, none is scheduler do be hidden, because autoHideAfter is 0
  3. the orange notification is shown, and the blue one, the red one, and the orange one are scheduled to be hidden after 1s.

The 2018.1.117 code does not feature this loop and the bug is not present.


Last Updated: 25 Feb 2020 14:19 by ADMIN
Created by: Gerard
Comments: 0
Category: Notification
Type: Feature Request

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:

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:

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.