Kendo UI for Angular and Kendo UI for jQuery complete package (all components, css, js) downloadable at once with documentation. Just the way how it was for old (ex: Kendo UI jQuery 2005) versions. No individual component download.
Hi, I was going through Treeview in angular 5. What I feel lacking in Treeview is search functionality. I would be very thankful if you can provide search functionality. Thanks
The current upload component does not support chunking or streaming which is important when dealing with large files.
Hi, Thanks for the great work on porting jQuery TreeView to pure Angular... If possible to port the drag & drop feature as well As a sidenote, maybe add TreeView category to this feedback page Thank you!
It is really hard to check change log for every component you have. Why not implement common change log for all components.
I already talk to Carl Bergenhem (Product Manager for Kendo UI) about that, and he reply:
Great suggestion! I’ll sync this with our web site team and try to see if we can create something like this!
As picture says more then 1000 words, I attach propose solution.
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:
The toolbar component works perfectly for our application header requirements. But: the default styles (here material theme with grey background and drop shadow) does not make sense. While it's not a problem to work around it...
Please allow us to add custom CSS classes to toolbar component. Example:
I have experience creating column groups at the top of a kendo grid, but I would now like to do something similar with row groups. I have attached a screenshot of an example of what I would like to accomplish. Is this possible with Kendo Grid?
It would be great if there was some way to customize the complete look and feel of the splitter control.
I would think this would be possible via a custom template, similar to how one does a cell template for the grid control.
Is there any way to set error focus on the selected items in multi select component.
And after that, user can take immediate action to update the value, say auto Open the drop down dialog and go to the selected item.
It would be great to have audio input button for the conversational UI. That would allow user to speak his utterance and then the component should be able to provide the audio input as a inputStream in PCM or Opus audio format.
That way will be possible to integrate the same with any provider.