Currently the datePicker and probably other controls that implement the rangeValidation property do not listen to changes on the rangeValidation input.
This is preventing whether range validation is enabled based on other form input changes during user interaction with the form.
Can this be changed so it listens on ngChanges?
The dropdowns should provide an easy way to have certain items in the list as inactive. The easiest way could be an attribute. In addition to [textField] and [valueField] an [inactiveField] could be added. If the assigned data field is a boolean the item in the list can be either enabled or disabled. Reason for this request is, that those value lists often are dynamic, meaning that an item in the list could be superseded by a new one. But the existing records in the database still could reference the older item, but new records should be prevented from selecting the new item.
When both virtual scrolling and grouping are enabled via the kendoGridGroupBinding directive, and the Grid is
navigable, focus is trapped in the header row when down or up arrow is pressed:
Focus any content cell
Press up/down - focus goes to the header cell of the respective column and is trapped in the header row
On a feedback portal search and paging is not working.
Open feedback portal and enter search criteria with more then five item. example
When you want to view result for second page, search is not preserved (it is empty).
The example does not work:
I want to filter the scheduler data but I had to add the OwnerId property to the node package interface in order to be able to do so... yet the sample data provided in the examples does include the ownerId, so im guessing all that needs to be done is to add it to the interface.
When opening a dialog with DialogService from an Observable (e.g. in order to initialize dialog with data from a http request) and ChangeDetectionStrategy.OnPush, the dialog is messed up. With ChangeDetectionStrategy.Default everything works fine.
For reproduction have a look to this StackBlitz: https://angular-9vmvyv.stackblitz.io
Scrolling like this : http://legacy.datatables.net/release-datatables/examples/basic_init/scroll_y_infinite.html Say you have 100.000+ rows of data. With classic or virtual scrolling, you allow your user to go to the last page very easily. It ends up with huge skip parameter, and disastrous load times from the DB. You don't want users to be able to run queries which are at the same time useless and very time-consuming server-side. What you really want is for your user to be able to browse a bit of the data with fast queries, and if he wants something else, he should filter data. Infinite scrolling gives him just that feeling.
I requested help in the Forum for an example of using JSDO in a Service under Angular for my grid.component.ts
Please look into building some sample source for an Angular / JSDO Service component.