Are you planning on implementing a feature to show a full year? same as the kendo-scheduler-month-view?

Can we expect this feature or do you can suggest a workaround using the existing functionality?

find below appcomponent.html code: <kendo-dropdownlist [defaultItem]="defaultYear"
 [data]="budgetYears"
[valueField]="budgetYears.value">
</kendo-dropdownlist>

and in appcomponent.ts file:
public budgetYears: Array<{ value: number }> = [
        { value: 2019 },
        { value: 2020 },
        { value: 2021 },
        { value: 2022 },
        { value: 2023 },
        { value: 2024 },
    ];

as mentioned above I have provided the mentioned codes but I am not getting the binded values. Instead of that I am getting [object Object]. Why it is so and where I am doing mistake. Please provide me a solution for this. Thanks 

I have a usecase where the initial selected item is no longer present in the choices.
With the current behavior, the initial value is not displayed and the dropdown is empty.
Would it be possible to display the initial value with a 'disabled' css class in the dropdown?

Same for multiselects, etc.

The Dropdowns, autocompletes and pretty much every component in the Kendo Angular 2 should allow the developer to specify a callback function in the [valueField] or the [textField] attributes so we can use complex objects with these components.  

This way, we could do this:
//template

<kendo-autocomplete [data]="nodes"

                        [valueField]="getDataValue"

                        [placeholder]="'search'"

                        class="search">

</kendo-autocomplete>

//class

public getDataValue(node: any): string {

  return node.getData().getName();

}

This functionality is available on almost every other component set out there, but is somehow missing from Kendo.  It makes the components almost useless outside of running simple plunkr examples that work with contrived data objects with very little depth.  In the real world, particularly with typescript, data object hierarchies are commonplace and this is simply a must have feature.

I think could be really useful to add pager component. It could be just same pager component used intrnally by grid. So easy development step i guess!

Issue: unable to filter data by itself written filter handlers.

Current implementation:

/**
 * A complex filter expression. For more information, refer to the [`filterBy`]({% slug api_kendo-data-query_filterby %}) method.
 */
export interface CompositeFilterDescriptor {
    /**
     * The logical operation to use when the `filter.filters` option is set.
     *
     * The supported values are:
     * * `"and"`
     * * `"or"`
     */
    logic: 'or' | 'and';
    /**
     * The nested filter expressions—either [`FilterDescriptor`]({% slug api_kendo-data-query_filterdescriptor %}), or [`CompositeFilterDescriptor`]({% slug api_kendo-data-query_compositefilterdescriptor %}). Supports the same options as `filter`. You can nest filters indefinitely.
     */
    filters: Array<FilterDescriptor | CompositeFilterDescriptor>;
}

Where filter descriptor has next available fields:

export interface FilterDescriptor {
    /**
     * The data item field to which the filter operator is applied.
     */
    field?: string | Function;
    /**
     * The filter operator (comparison).
     *
     * The supported operators are:
     * * `"eq"` (equal to)
     * * `"neq"` (not equal to)
     * * `"isnull"` (is equal to null)
     * * `"isnotnull"` (is not equal to null)
     * * `"lt"` (less than)
     * * `"lte"` (less than or equal to)
     * * `"gt"` (greater than)
     * * `"gte"` (greater than or equal to)
     *
     * The following operators are supported for string fields only:
     * * `"startswith"`
     * * `"endswith"`
     * * `"contains"`
     * * `"doesnotcontain"`
     * * `"isempty"`
     * * `"isnotempty"`
     */
    operator: string | Function;
    /**
     * The value to which the field is compared. Has to be of the same type as the field.
     */
    value?: any;
    /**
     * Determines if the string comparison is case-insensitive.
     */
    ignoreCase?: boolean;
}

export interface FilterDescriptor {
    /**
     * The data item field to which the filter operator is applied.
     */
    field?: string | Function;
    /**
     * The filter operator (comparison).
     *
     * The supported operators are:
     * * `"eq"` (equal to)
     * * `"neq"` (not equal to)
     * * `"isnull"` (is equal to null)
     * * `"isnotnull"` (is not equal to null)
     * * `"lt"` (less than)
     * * `"lte"` (less than or equal to)
     * * `"gt"` (greater than)
     * * `"gte"` (greater than or equal to)
     *
     * The following operators are supported for string fields only:
     * * `"startswith"`
     * * `"endswith"`
     * * `"contains"`
     * * `"doesnotcontain"`
     * * `"isempty"`
     * * `"isnotempty"`
     */
    operator: string | Function;
    /**
     * The value to which the field is compared. Has to be of the same type as the field.
     */
    value?: any;
    /**
     * Determines if the string comparison is case-insensitive.
     */
    ignoreCase?: boolean;

     /** --------------- ADDITIONAL DATA --------------- */
 
     /**
     * Manages filtering operations with data for single row
     */
    handler?: (dataItem: T) :  Observable<boolean> | boolean;
    /**
     * Filter name to display on grid
     */
    name?: Observable<string> | string;
}

Please make autocomplete list item fully customizable as what it is in jQuery version. I would like to implement something like what it's showing below.

Hi,

we would like a feature to reverse the Cancel and Set buttons in the DateTimePicker, so that the Set button is positioned at the left instead of at the right (see attached image).

This is mainly for consistency and local culture reasons, as Windows dialogs also do this (put the positive answer at the left).

Kind regards,

Ludwig

Kendo Grids for Angular has the ability to remove operators by using `[showOperators]="false"`, however this keeps the button visible.

We would like the option to also hide/remove the clear button.

Our product management would like to make the input field of the Conversational UI a multi-line field so agents can see several sentences of what they are typing and scroll vertically rather than horizontally.  We have tried many CSS settings but can't seem to affect the height of this embedded field.

After contacting support, I was told that the desired behavior cannot be achieved with the currently rendered DOM of the Conversational UI component. The input element should be replaced with a textarea in order to allow wrapping its value on multiple lines.

Please consider adding this feature to your roadmap.

Before we started using kendo ui, we implemented this slidemenu. - https://www.primefaces.org/primeng/#/slidemenu
So far I haven't been able to find anything comparable within kendo ui, but the closest thing is https://www.telerik.com/kendo-angular-ui/components/layout/drawer/how-to/hierarchical-drawer/

The drawers could slide between options, instead of expanding out into the page.

Martin, on your team, managed to put together https://stackblitz.com/edit/angular-ckjeuc?file=app%2Fapp.component.ts which is awfully close to accomplishing what we're aiming for, but is lacking the smooth animations between menu layers that we'd like. Ticket ID: 1448501

Hello,

we want to show filtered data in the options list of the dropdown component and request a feature, to provide a filter callback function or the possiblity to pass different data sources to the component.

The use case is, that the dropdown should show existing values but when opening the dropdown list, the user should only be able to select a subset of the data source. Yes there is the possibility to disable items, but we want to complete hide them as a choice.

Currently we apply the workaround to filter the data on the open event and reset the data on the close event but we think, that this can be a common feature for the dropdown list.

Thank you!

I would like to request additional keyboard navigation functionality with the grid.  We are using the grid as a sort of spreadsheet, for teachers to enter grades.  Teachers want to move down the column in the grid by pressing the enter key after typing each grade, in order to move their focus to the field below.  After pressing enter, the field below should be focused and editable.  When pressing enter at the bottom of the column, focus should be brought to the top of the next column.  Using shift+enter would move the focus up a row, and if at the top of a column, would bring focus to the bottom of the column to the left.

This behavior differs from the current grid keyboard navigation, I believe, in that we need the navigation to be present and the fields within each cell to be editable at the same time.  The teacher will not want to switch between navigating and editing, they want to quickly enter their scores going down the column, like a spreadsheet.

We have tried to implement this ourselves and have been mostly successful, but the area where we are having issues beyond our control is when using virtual scrolling.  As the grid swaps out its rows for the next set of data, the user's focus is moved to a different cell where we do not wish to have the focus at that point.  We have attempted to immediately move the focus back to the cell it should be in, but the user can type faster than we are able to regain control of the focus and we wind up with grades in cells where they shouldn't be.  We have tried using the pageChange event, but that occurs after the page has already changed and the focus has already been moved somewhere we don't want it.  If you have any suggestions for dealing with this in the meantime that would be most helpful.

Thank you!