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.
Please support out of the box support for modality. I know there is how to, but out of the box, for such basic feature seems reasonable.
Also suggested how to doesn't work for windows initialised through service.
This would also align Angular Window component with KendoUI Window component modality.
I would like to move dialog (because there is some content behind I need to see in order to fill form in dialog).
It would also be great if it could be resizable. If you have an input component inside dialog, you could set width to 100%.
It would be a good feature if you allowed the same customisation options for the built-in filter-menu components, like the TreeList component.
Hi,
It will be a good component enhancement if selection and multi selection was introduced to the ListBox component. Like Kendo UI for React and jQuery:
https://www.telerik.com/kendo-react-ui/components/listbox/selection/
https://docs.telerik.com/kendo-ui/api/javascript/ui/listbox/configuration/selectable
Thank you for your consideration.
Provide the ability to customize the drag handle for the row reordering of the TreeList, similar to the available Grid feature:
Enhance the Spreadsheet component by providing the double-click fill down functionality available in Excel. For reference:
Hi, Team!
I would like to request both prefix and suffix templates that would allow users to display various elements as adornments in the Date Inputs components.
Currently, when a MaskedTextBox is emptied while the includeLiterals property is set to true, the control returns a string that still contains the literals defined by the mask. This behavior makes it difficult to distinguish between a genuinely empty input and one that contains only literals.
Expected behavior:
When the user clears the input, the MaskedTextBox should return either an empty string ("") or null, even if includeLiterals = true.
Suggested improvement:
Introduce an option on the MaskedTextBox that lets developers choose the desired behavior when clearing:
Keep literals (current behavior),
or Return empty string / null (proposed behavior).
Why this matters:
It complicates validation and data processing, as developers need to add extra logic to detect and strip literals.
In many real-world scenarios, an empty field should semantically represent no input, not a string with placeholder characters.
Making this configurable would give developers flexibility without breaking existing behavior.
Reproducible example:
I’ve created a working example in StackBlitz that demonstrates the issue.
Currently, it is not possible to include additional buttons next to the send button in the Conversational UI.
Having such feature will provide a way for adding more action buttons such as file/image/video selection etc.
Such a directive will help in customizing the content of the attachments and I would also like to create a horizontal list that expands downward which will eliminate the scroll button.
Please provide row virtualization as addition to the current virtual scrolling functionality.
Current behavior
Virtual scrolling is currently tied to the pageSize. This is not always desirable as page size can be much higher than the visible area to optimise for network latency.
For example if the pageSize is 200 rows and the grid is only 10 rows high we'll be rendering 190 more rows than needed at initialization time.
Expected behavior
Virtual scrolling should include an option to render only the visible rows at any given time.
Current behavior
The developer must measure the Grid row height in the browser and set it to the `rowHeight` in order for virtual scrolling to work correctly. Setting an incorrect value can lead to subtle errors - glitches during scrolling or inability to scroll down to the last row.
The row height may change as a result of a styling adjustments and is not guaranteed to be identical across browsers and devices. This makes the current workflow tedious and error-prone.
One of the following approaches can be used to solve this issue:
- The Grid should take accurate measurements of the row height at run-time. The developer should still be aware that row height is constant . This is the preferred approach as it does not change current behavior, instead the set `rowHeight` value is ignored.
- The set `rowHeight` should be applied as inline styles. This is a more risky approach as it will change the appearance of the Grid.
Provide a built-in column menu component (like in the Grid and TreeList) for the base column menu functionalities - filter, sort, sticky. This way, custom column menus can be easily created when you want to keep some of the default options.
Right now, I need to create all components, even those for filter and sort, from the ground up, but available as:
kendo-grid-columnmenu-filter
kendo-grid-columnmenu-sort
is the Grid.
Hello,
I would like to request a way to have the selected/unselected column menu sorted separately from the table's columns.
Here is our table which demonstrates the current behavior.
When first rendered on the page:
After re-arranging the columns:
However, it'd be nice to have the column menu sorted separately from the table's columns. Thank you.