Custom Timezone (e.g., UTC): Allow the ability to set a custom timezone, overriding the system clock for consistent time handling (e.g., UTC).
Timezone-Aware "Now" Button: Enable the "Now" button to respect the selected timezone. For example, if the timezone is set to UTC and the current UTC time is 12:00:00, clicking "Now" should display 12:00:00 instead of the local time.
These features would improve flexibility for timezone-specific applications and ensure consistency in timestamp-based operations. Thank you for considering this request!
The Grid provides column spanning by default, but the change is applied to all rows:
https://www.telerik.com/kendo-angular-ui/components/grid/columns/spanned
A good addition to the Grid would be to provide conditional columns spanning where some rows are normal while others - have spanned columns such as:
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.
Provide support for dynamic label positions for the Donut chart.
Some labels to be displayed inside the Donut, and other (which couldn't fit) to be outside, similar to:
Hi Team,
Currently, the zoom property is only responsible for setting the initial zoom level of the document inside the PDFViewer component. I would like to request an option that would allow setting the zoom property dynamically/programmatically.
Hi Team,
Currently, when loading large PDF files with numerous pages, there seems to be a delay in the search and zoom functionalities.
I would like to be able to load the pages of the PDF one at a time and handle the pageChange in order to load the next page.
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.
Kendo's Angular components that have optional inputs are not built correctly.
For example on the `kendo-avatar`component the input `imageSrc` is defined like this:
@Input() imageSrc: string;however, since it is an optional input it should be defined like this:
@Input() imageSrc?: string;
// or
@Input() imageSrc: string | undefined;
Hi Team,
I would like to request the toolbar data validation tool like this Kendo UI for jQuery demo to be included in the new Angular component.
Thank you!
Hi,
We've noticed a significant difference in how the "Select All" checkbox functions in the Grid and TreeList when paging is enabled.
Our application uses both components, and users expect them to behave consistently. However, we’ve identified several issues:
1. Inconsistent User Expectations
In the Grid, "Select All" applies only to the current page.
In the TreeList, "Select All" applies to all pages, including hidden rows.
This inconsistency can confuse users who switch between these components, leading to unexpected behavior and frustration.
2. Confusing Bulk Actions
In the Grid, users understand that selections are limited to the visible page.
In the TreeList, users might unknowingly select thousands of records, potentially causing unintended bulk updates or performance issues.
3. Risk of Data Loss or Errors
Users assuming the TreeList behaves like the Grid might:
Select all rows, perform an action (e.g., delete or update), and unintentionally affect all pages instead of just the current one.
This can lead to accidental data loss or incorrect modifications.
We need a consistent approach to "Select All" behavior across both components to prevent confusion, errors, and performance issues.
Expected behavior
If "Select All" is checked, it should:
- Select all visible rows on the current page.
- Select all children of selected parents, even if those children are on other pages.
- Maintain selection when navigating to another page.
If it should be submitted as a bug, please let me know.
Currently, the kendoRippleContainer directive takes effect only on the following elements - buttons, checkboxes, and radio buttons:
It would be great to have the ability to apply the Ripple to other various elements as well.
Provide a built-in feature to collapse or expand child columns of the group column similar to ag-grid.
Workaround using the header template: https://stackblitz.com/edit/angular-orwl7wza
This will enhance the PDFViewer usability as the Toolbar provides many built-in features like responsiveness, tool customizations, etc., which will add extra value to the component.
The component is already used internally in the Editor and Spreadsheet.
Hi,
It would be a good addition to the Gantt component if a progress completion indicator is rendered on the tasks as in Kendo UI for jQuery.
