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%.
When scrolling to the right and to the bottom the columns and rows are not aligned any more.
This is already visible in the example in the documentation: https://www.telerik.com/kendo-angular-ui/components/gantt
Hello,
I tried to implement this new feature : https://www.telerik.com/kendo-angular-ui/components/grid/scroll-modes/virtual#controlling-the-expanded-state-of-all-root-level-groups
You can see in the demo that if you remove all grouping, the content is now limited to 50 lines instead of displaying the whole 1000.
I found a workaround by expanding all before removing the grouping but it is not very user friendly.
If you can patch it ASAP that would be great.
And thank you to finally have pushed this long awaited feature !
First of all, thank you for providing the state management feature. For me it's one of the most important features of a grid component.
But unfortunately it fails to restore the columns state. This is because each time a grid component and it's columns are instantiated, new IDs are created for the columns. When loading state the columns are identified by their IDs.
When a column is persisted with e.g. id 'k-grid-column-1' and the grid will be destroyed and re-created, then the new column ID is not identical with the old one. Thus restoring the column's state will fail.
Please have a look to this StackBlitz example: https://stackblitz.com/edit/angular-vauqyshn?file=src%2Fapp%2Fapp.component.ts
A possible workaround is to save also the column's field property and later use it to re-map the saved id to the new id.
A better solution may be to extend the GridColumnComponent with something like a "PersistenceKey" property, which will be used for identifying a column. A directive may also work. Otherwise generating non transient unique ids for the grid columns will also work.
Best regards,
Holger
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.
If a table wraps to the next page on a PDF export, and a column has a rowspan extending to the next page, the rowspan column is not rendered on the following pages. This causes other columns to move left on the next page, so headers and cells do not match anymore.
StackBlitz sample: 6quahnzd (duplicated) - StackBlitz