1. Run application and open the schedule component
2. Start drag the element on schedule to new place and drop it.
After that whole schedule component will blink(in Chrome, for example, all OK).
I found an issue with the kendo-window component. Sometimes when you have a window component with an embed element inside it and you start dragging the window and then click inside the embed element (In the example a PDF viewer), after that you click again in the window’s title bar the window is stuck in the dragging state and it keeps following the mouse pointer even when you already release the mouse button.
It is an odd behavior and we need to know how to stop this, but without disabling the dragging functionality for the kendo-windo.
Here is the repro-case in stackblitz: https://stackblitz.com/edit/angular-jqjemx
Perhaps you need to try clicking over several times in order to reproduce this behavior.
The problem is that in our application the pointer position remains inside the embed element and we can’t click the title-bar again to release the dragging mode.
In Version 74.0.3729.108 (official Build) (64-Bit) of chrome, a defined grid with no predefined style property does not scroll properly.
There is a live-demo on Stackblitz at https://stackblitz.com/edit/angular-b38r7s-jzsgty
This is a fork of the demo example from the kendo-angular-ui documentation available at
In the example, the scrollable grid was defined with a height property. This does not feet to our requirements, as we need a grid component that should flex according to the outside or parent container.
This problem occured after the update of chrome browser from 73.0.XXX to the version 74.0.3729.108
The problem is fixed when we defined a grid with a height property like [style.height.%] = “100” but according to the documentation the grid should flex automatically without this property.
1. Try to use the grids column menu for filtering
2. Click the column icon => popdown menu opens
3. Click the filter oder column icon inside the menu => nothing happens
I can't even open up your docs using IE11, it just loads forever: