Provide an option to customize the tooltip that appears while dragging a task in the timeline view.
Currently, it is not possible to enter a date that falls exactly on a Daylight Saving time.
Check the following example where it is not possible to enter 3 for the hours' section (it is also not possible to select 3 from the TimePicker popup):
https://stackblitz.com/edit/angular-nstdolh5-xfiws9nr
That behavior is expected as there is no such time in the Bulgarian time zone. Daylight saving time begins on 30 March 2025 03:00 when the time is moved 1 hour forward.
The demonstrated undesired behavior for the specific date will be reproducible only if the example is opened in the specified time zone. But the same behavior is valid for any other date that falls on Daylight Saving time in other time zones.
We should decide on what the expected behavior is for such cases. For example not allowing entering the value, displaying an error, auto-switching to the real hour (4 AM), etc.
I would like to modify the crosshair tooltip to display the interpolated y value for the given x position of the crosshair (see data below the chart)
It would be great to have support for collaborative editing in the Editor. This could include a helper function to facilitate collaboration, similar to ProseMirror’s or Yjs’ implementations. This would enhance real-time collaborative capabilities for users, allowing smoother shared editing experiences.
Examples:
jQuery version has MeasuresAxis allows to switch measures between 'columns' and 'rows', can you please provide the same feature on Angular version.
See kendo.data.PivotDataSourceMeasureOptions.axis for reference from jQuery version or https://docs.telerik.com/kendo-ui/api/javascript/data/pivotdatasource/configuration/measures#measuresaxis
Provide the ability to customize the drag hint for the row reordering of the TreeList similarly to the available Grid feature:
When using Kendo UI for Angular's ComboBox or other DropDowns in Reactive Forms, clicking the 'X' to clear the control removes the associated value from the FormGroup entirely. This behavior differs from other frameworks like React and Blazor WASM, where the control remains but is set to null. Currently, developers must manually handle this event to retain the control in the form. It would be beneficial if clearing the value only set it to null instead of removing the control from the FormGroup.
Expected Behavior:
Clearing the form when using the clear button should act like a form reset.
Currently, when setting the value property of the TimePickerComponent programmatically (without using two-way binding in the template), the control does not update its displayed value until it gains focus. This behavior is inconsistent, especially when compared to other controls that properly reflect programmatic value changes.
Example - https://stackblitz.com/edit/angular-nhg2x1b9-d7f5bhh9?file=src%2Fapp%2Fapp.component.ts
The ListView component currently has an endless scrolling feature that allows the developer to load more items on demand. However, when all items are loaded upon continuous scrolling, there can be some issues in performance due to the large number of rendered DOM elements at the same time.
For this reason, providing a virtualization functionality that renders only a limited number of elements at a time will be useful in improving the performance of the ListView when a large number of items are used.
Provide the ability to customize the cells' content of the Spreadsheet. SImilar to the custom cell editors of the Kendo jQuery Spreadsheet:
https://demos.telerik.com/kendo-ui/spreadsheet/custom-editors
Currently the imageSrc input property only accepts string as value. Allow the property to accept and work with blob URLs as well. Additionally, as the property accepts only string as value, the URL cannot be sanitized as sanitizing it always results in a SafeUrl type.
Currently, the NumericFilterMenuComponent has a default filterDelay of 500ms. So, in some scenarios where a value is entered and the Enter key is pressed very quickly, the component may not be able to catch the new filtering condition and create a new filter descriptor with the entered value.
It would be great if the component is enhanced to take into account the last entered value in such scenarios despite the defined delay.
It would be a useful feature if the TreeList had an isRowSelectable callback similar to the Grid.
https://www.telerik.com/kendo-angular-ui/components/grid/selection/row-selection#disabling-the-selection-for-specific-rows
https://www.telerik.com/kendo-angular-ui/components/grid/api/gridcomponent#isrowselectable
We have a scenario where we have inputs inside the sortable component. As the user types into the input the focus is lost constantly this is due to the Sortable component being re-rendered unnecessarily by Angular change detection. You can see an example here
Angular is moving towards immutable data structures and it is often the recommended practice. Therefore I believe the sortable component should be able to handle the scenario provided. This should be achievable by internally using a trackBy function to help Angular recognise when data hasn't changed. This should be accompanied by allow the consumer to provide their own function for tracking.
A similar issue was raised 5 years ago but wasn't adopted. In my opinion given the massive advancements in Angular and the introduction of Signals this becomes a more pressing issue now and arguably moves from the realm of feature request to bug.
While the grid is initially loading data, the "No records available." message is confusing and provides no useful information.
Expected behavior - when the grid is initially loading, don't display the message as the rows/data might very well appear
To reproduce basically just go to the grid demo page (refresh if needed) and pay attention to the grid loading: https://www.telerik.com/kendo-angular-ui/components/grid/data-binding/
Example in our project - intuitively you'd think that the grid has no records until you see the loader; in any case, the message looks out of place:
Change the default vertical Stepper by enhancing the layout like the Material Stepper -rendering the content in between the steps:
https://material.angular.io/components/stepper/overview
Hi,
We are facing a notable poor performance in tree view when loading about 1500 tree nodes with custom template and it is taking approximately 32 Seconds to load it. You have already provided load more option to virtualize data but this is not so user friendly and suggested listview which has virtualization also not good fit to replace treeview. I wonder how this virtual scroll is missed in tree view!!. It is very important component to our project If you could provide this feature will be great.
Thanks& regards,
Ramesh M
If you expand a tree node with 1000 items in it, and that tree has an ng-template the performance is very poor. It takes 7 seconds on my machine, see here https://www.telerik.com/forums/slow-treeview-with-large-datasets Please add virtualisation to the TreeView so that not so many DOM elements (and therefore ng-templates) need to be created.
It seems that whenever a task crosses the date where the daylight saving time switch appears everything on the gantt's week view gets shifted by 1 hour.
This stackblitz shows 2 Gantts. The first one has correct positioning, the second one appears to be bugged.
In this picture, you can see that in the 1st Gantt `Item 1` is slightly shifted to the right and covers Thursday and Friday. That's because its date is specified in UTC as `2025-04-03T00:00:00.000Z` which, for me in the UK, will result in `01:00:00.000`.
However, in the second Gantt `Item 1` now fully covers Thursday and doesn't extend to Friday even though the start and end dates are the same as in the first Gantt.
You might get slightly different positioning based on your time zone. The description is written based on the UK time zone.
It also affects drag-and-drop marquee. If you try to drag the right side of item 1, you'll see that it will show Saturday even before it starts covering Saturday.
Expected behaviour: Item 1 has to be positioned identically on both timelines