The date range picker is not closing when tabbing through inputs when the picker is appended to the 'component'. It also seems that once the date range picker loses focus, it does not close by clicking anywhere else in the document until it regains focus again or the document loses focus.
I reproduced it in Stackblitz and attached a video. In the video there is a button after the date picker that logs to the console when it gains focus. Focus starts at the top of the document, start tabbing until the date range picker pops up, then continue tabbing through the date range picker until the button below the picker gains focus. As you can see the date range picker does not close. Here is the Stackblitz editor link to this: https://stackblitz.com/edit/kendo-daterange-bug?file=app/app.component.ts
Thanks!
Mitchell
When setting the Checkbox component to disabled while the form is marked as touched, the k-invalid class is applied to the checkbox control.
That's because of the implementation of the isControlInvalid property:
public get isControlInvalid(): boolean {
return this.control && this.control.touched && !this.control.valid;
}
According to the Angular source code:
/**
* A control is `valid` when its `status` is `VALID`.
*
* @see {@link AbstractControl.status}
*
* @returns True if the control has passed all of its validation tests,
* false otherwise.
*/
get valid(): boolean;
So valid() returns false when `status` is DISABLED.
The `isControlInvalid`property should better implemented like this:
public get isControlInvalid(): boolean {
return this.control && this.control.touched && this.control.invalid;
}
Please check this Stackblitz: https://stackblitz.com/edit/angular-dznoe1xj?file=src%2Fapp%2Fapp.component.ts
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.
I'd like to report that my issue linked in Duplicated item was not fixed:
Closed bug: https://feedback.telerik.com/kendo-angular-ui/1484071-scheduler-event-editor-recurrence-editor
My bug marked as duplicate: https://feedback.telerik.com/kendo-angular-ui/1657303-scheduler-some-events-are-incorrectly-duplicated-despite-the-rules-written-on-them
It can still be reproduced in new version 17.3.12
https://stackblitz.com/edit/angular-pusn73-en4gpcjt?file=src%2Fapp%2Fapp.component.ts
The event with recurreneRule that suggests that this event appears on each Tuesday till 20201014 is visible on Wednesday 14th.
Hello,
It would be great to have the same state management functionality in the TreeList component as provided for the Grid component.
https://www.telerik.com/kendo-angular-ui/components/grid/persist-state
As a minimum saving and restoring columns state (visibility, width, order, sort, ...) should be provided.
Best regards,
Holger
When a custom element is added, like a button, the user cannot use the internal navigation of the Scheduler. This is resolved in the Grid by a directive, and here it can be the same.
Hi,
in a Treeview bound to flat data (probably does not matter), if I have 3 items, and I drop the first 2 in the last, the loading indicator is stuck.
Stackblitz repro: https://stackblitz.com/edit/angular-xiwrcwsx?file=src%2Fapp%2Fapp.component.ts
Can you please take a look at it?
Best regards,
Michael
Hi,
we would like to submit a feature request for the grid component:
We would like the tds (generated when the kendoGridGroupHeaderColumnTemplate is specified) to be sticky if the related column is sticky (since right now, if i stick a grouped column, the group row td corresponding to the sticky /locked column scrolls with the rest of the row instead of being sticky as we would expect)
here's an exaple of the behavior we are encountering:
https://stackblitz.com/edit/angular-lgbef6c1?file=src%2Fapp%2Fapp.component.ts
Best regards,
Claudio Salvatore Conte
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%.
Provide sticky rows functionality for the TreeList, just like the one available for the Grid:
https://www.telerik.com/kendo-angular-ui/components/grid/rows/sticky#setup
It would be useful to see the parent row when scrolling through its child rows.
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.