Currently, the Button component supports appearance options such as size, fillMode, and rounded.

This request is about a way to set those appearance options globally for the entire app, in a single location, so that the user does not have to pass all of these settings every time they use a button.

I know this could be achieved by wrapping the Button component in another component, but that may lead to an unnecessary performance hit.

Another option would be to use the ThemeBuilder and set some variables, but that would not behave in the exact same way as the appearance options - for example, it is not so dynamic.

The kendo scheduler when opened in the mobile view the events tittle inside the month view texts are broken and hide in responsive design.

The user did not see the full event tittle texts in month view in responsive Design. 

please refer below  attachments here.

The Scheduler recurrence editor numeric inputs automatically change leading 0 inputs via keydown or pasting to 1's or empty values. 

Extend the ability to disable the mandatory autocorrection for all recurrence editor inputs so any numeric value can be entered.

When I create a widget and design widget with image field.

Step 1: I use this widget in CMS=> click edit content => select data for the image field.

Step 2: Click advanced to see the id of image 

Step 3: I select simple to view image agian =>  the image has clear item. 

I don't know how it happen.

Please help me about this issue

Please provide a mechanic for dynamic messages translations and/or more seamless integration with established third-party libraries like ngx-translate.

Currently the only available option is using a customized messages service, but this approach has multiple shortcomings

- all messages for all locales need to be recreated one by one in the service

- is not integrated with third-party libraries used to translate the rest of the application

A detailed discussion regarding the necessity of similar enhancement is available in the following GitHub thread:

https://github.com/telerik/kendo-angular/issues/362

P.S.: A possible workaround available for integration with ngx-translate involve adding the desired Kendo messages in the JSON files containing all translations for each supported language, and using the custom messages service to obtain and return the ngx service translation. Recreating the page each time the JSON data for the respective language is loaded is necessary to ensure that the correct messages will be available and used in the Kendo components.

The following example demonstrates a sample implementation of this approach:

https://stackblitz.com/edit/angular-kzirzx?file=src%2Fapp%2Fapp.component.ts

Add selectOnFocus option for AutoComplete, ComboBox and MultiColumnComboBox.

The same is available for the TextBox component:

https://www.telerik.com/kendo-angular-ui/components/inputs/api/TextBoxComponent/#toc-selectonfocus

Re https://github.com/telerik/kendo-angular/issues/3649

The FilterableComponent has been removed from the dropdowns public API.

This is important to us as it allows us to create a directive that targets all the filterable components, similar to FilterDirective.

Can this be made public?

Please introduce an option to perform accent-insensitive search using the Grid built-in string filtering.

If a user attempts to have a Kendo Grid column filter match Pare, ideally it should find Paré (with the accented é).

A similar FR is already available for the DropDownList:

https://feedback.telerik.com/kendo-angular-ui/1503741-filtering-should-support-accent-insensitive-search

https://stackblitz.com/edit/angular-oc4d4c-ss8dyk?file=app/app.component.ts

1. If a detail row is expanded, the entire virtual scroll fails - showing whitespace/not loading new data once you scroll enough to trigger pagination/new dataset load. It remains broken even after collapsing the details row.
2. Scroll down and filter - you see white area. You need to scroll until it triggers data load to fix it.

Hi

It would be great if KendoGrid export to Excel and PDF like excelExport, saveAsExcel, saveAsPDF etc should had options to include all records of the grid and to apply the persistent filters, grouping, sorting etc

Something like:

<kendo-grid-excel fileName="test.xlsx" filteredData="true" allRows="true">

</kendo-grid-excel>

filteredData="true"
Exports exactly what the user has filtered, sorted, grouped, etc. and sees in the view

allRows="true"
Ignores the paging and includes all the data/rows

Currently toODataString constructs the entire query string used to make a request. When API endpoints are automatically generated (using swagger/OpenAPI for example), this makes toODataString less helpful. I would like a function that exposes the individual properties generated by toODataString

For example, toODataString currently produces something like

'$skip=0&$top=20&$orderby=quantity&$filter=date ge 2020-01-01T00:00:00.000Z'

I'd like something like toODataObject that produces something like

{$skip: 0, $top: 20, $orderby: 'quantity', $filter: 'date ge 2020-01-01T00:00:00.000Z'}

so that I could pass individual properties as parameters to generated API functions.

Thanks.

Would really like a Kendo UI version of the Chip Input like the one from Angular Material https://material.angular.io/components/chips/overview#chip-input

I was surprised looking through all the components that something like this didn't already exist

The nodeViews feature of proseMirror can't be used if not exposed as an input as it should be set in construction of the EditorView which is done internally the component.

We would like to supply it as an input to your component

    .k-coloreditor-header {
        padding: $coloreditor-header-padding-y $coloreditor-header-padding-x 0;
    }

The style rule uses the two variables - with x and y respectively, yet has a hardcoded 0px value as a third parameter.

This causes x to only apply top padding, which is misleading.

Currently the Filtering functionality of the Kendo UI for Angular TreeView is not compatible with the built-in Drag'n'Drop.

Please make it possible to use both directives simultaneously.