Proposal

CellCloseEvent<T> should provide dataItem: T

Why

Currently the CellCloseEvent dataItem is typed as any. This could be the default, but adding a generic type here would allow strong typing in the event handler.

Currently the Grid Filter menu logic is "and" and there is no built-in option for changing it even when using the configurable filter menu components in the Filter menu template.

It would be nice having an option to configure the default logic as well as to limit the list of options to only "And"/"Or" or prevent the end user from changing the programmatically set filtering logic.

As a workaround for setting the initial logic, the developer can use the logicChange method, e.g.:

https://www.telerik.com/forums/default-filter-menu-logic#4935605

Currently, the Selection feature behaves strangely with the Keyboard Support enabled, see [demo](https://plnkr.co/edit/hTOg7Flx5Fnm63jJ6CgX?p=preview):

* Enter, Ctrl+Enter and Shift+Enter select the rows, but do not function if the cell has focusable components
* Space works only on the checkbox column
* Ctrl+Space, Shift+Space do not work at all

Ideally, the Grid should support the following shortcuts when the Selection and KB Navigation are enabled:

* Select the current row on Space, regardless of the cell content
* Support Ctrl and Shift modifiers for Space

* Shift + Up/Down Arrow for adding/removing the next/last row to the selection.

Similar to the TreeList KB navigation:

https://www.telerik.com/kendo-angular-ui/components/treelist/keyboard-navigation/

Please provide support for spanned columns with multi-column headers combining the already existing features:

https://www.telerik.com/kendo-angular-ui-develop/components/grid/columns/spanned/

https://www.telerik.com/kendo-angular-ui-develop/components/grid/columns/headers/

Overcoming the last listed limitation would be nice:

https://www.telerik.com/kendo-angular-ui-develop/components/grid/columns/locked/#toc-known-limitations

Currently when I click the horizontal scrollbar button which is present at the left side or right side of the scroll bar then the columns are scrolled as a regular table.

It will be nice to move from one column to another column instead.

Hi Team,

Requesting a feature to grid rows merge like the below example,

Thanks!

Currently, the NumericFilterMenuComponent has a default filterDelay of 500ms. So, in some scenarios where a value is entered and the Enter key is pressed very quickly, the component may not be able to catch the new filtering condition and create a new filter descriptor with the entered value.

It would be great if the component is enhanced to take into account the last entered value in such scenarios despite the defined delay. 

Hi,

It will be a nice feature to have the ability to customize the drag hint of the built-in row reordering similar to the hintTemplate.

It would be nice to have a feature to remove some operator from the grid filter built-in functionality as a global setting so that they apply across all grid columns without needing to repeat this customization for each column.

I understand that Kendo supports this functionality as described, but my expectation is to configure it as a global setting rather than on an individual basis. This would significantly simplify configuration in cases where multiple grids or columns are involved.

Add a locale formatting option to the Grid pager elements, similar to the functionality available in the DropDownList within the Grid pager.

Related to - https://feedback.telerik.com/kendo-angular-ui/1674278-grid-pager-numbers-do-not-appear-to-respect-internationalization-locale

Workaround using the pager template - https://stackblitz.com/edit/angular-rvvry94x-8jfbjfbp

Hi, Team!

I would like to request the introduction of the Ctrl + A keyboard shortcut as an approach for selecting all rows inside the Grid component.

Could we have a turnkey solution which allows to disable a row selection which takes care of disabling only the relevant selection checkboxes and handle properly the "Select all" checkbox state (in header).

With CheckboxColumnComponent field which allows providing dataItem field name or predicate function.

<kendo-grid-checkbox-column showSelectAll="true" disableSelection="isDisabled">
</kendo-grid-checkbox-column>

<kendo-grid-checkbox-column showSelectAll="true" [disableSelection]="isDisabledPredicateFunction">
</kendo-grid-checkbox-column>

OR

If you don't want to add more selection concerns into CheckboxColumnComponent this field could be specified in your SelectableSettings as well:

public selectableSettngs: SelectableSettings = {
    enabled: true,
    checkboxOnly: false,
    mode: 'multiple',
    cell: false,
    drag: false,
    rowEnabled: mySelectableRowPredicateFunction
}

rowEnabled field could something like this:

export declare type RowEnabledSelectionFn = (context: RowArgs) => boolean | boolean;

export interface SelectableSettings {
    //...
    /**
     * Determines if row selection is allowed.
     *
     * @default true
     */
    rowEnabled?: RowEnabledSelectionFn;
}

Thank you

Currently, there is only an option for setting a label for the filter cell operators DropDownList available in the CustomMessagesComponent:

• https://www.telerik.com/kendo-angular-ui/components/grid/api/custommessagescomponent#filtercelloperatorlabel

Provide a similar property for setting a custom value for the title attribute of the filter cell operators DropDownList through the custom messages attribute bindings.

As the FilterInputWrapperComponents set currentOperator(value: string) uses a hard coded list of operator values (isnull isempty isnotnull isnotemty), it is impossible to create a custom FilterOperator that has no search string - so we can't have isnullorempty isnotnullorempty (or isblank/isnotblank).

Please introduce a requiresSearchValue on the FilterOperatorBase class and make sure FilterInputWrapperComponents does decisions based on that.

Please introduce a isnullorempty/isnotnullorempty filter operator (for strings).

Additional context/sample usage:

 <kendo-grid-column title="Employee / Prospect" field="Name" width="160">
            <ng-template kendoGridCellTemplate let-field let-value let-dataItem>
                <span *ngIf="dataItem.IsProspect" class="pull-left">{{dataItem.Name}}
                    <p class="prospect-indicator pull-right" data-letters="P"></p>
                </span>
                <span *ngIf="!dataItem.IsProspect">{{dataItem.Name}}</span>
            </ng-template>
            <ng-template kendoGridHeaderTemplate let-column>
                <span title={{column.title}}>{{column.title}}</span>
            </ng-template>
            <ng-template kendoGridFilterMenuTemplate let-filter let-column="column" let-filterService="filterService">
                <kendo-grid-string-filter-menu
                    [column]="column"
                    [filter]="filter"
                    [filterService]="filterService">
                    <kendo-filter-eq-operator></kendo-filter-eq-operator>
                    <kendo-filter-neq-operator></kendo-filter-neq-operator>
                    <kendo-filter-contains-operator></kendo-filter-contains-operator>
                    <kendo-filter-not-contains-operator></kendo-filter-not-contains-operator>
                    <kendo-filter-startswith-operator></kendo-filter-startswith-operator>
                    <kendo-filter-endswith-operator></kendo-filter-endswith-operator>
                    <kendo-filter-isblank-operator></kendo-filter-isblank-operator>
                    <kendo-filter-isnotblank-operator></kendo-filter-isnotblank-operator>
                    <kendo-filter-isempty-operator text="xIs blank"></kendo-filter-isempty-operator>
                    <kendo-filter-isnotempty-operator text="xIs not blank"></kendo-filter-isnotempty-operator>
                </kendo-grid-string-filter-menu>
            </ng-template>
        </kendo-grid-column>

Currently the Grid checkbox column selection does not allow for selecting a range of rows via shift-click.

As this seems to be a behavior that users expect, based on a similar experience with popular applications like for example Outlook and Gmail, we can consider introducing this behavior in the Grid too.

For example:

When we click on a check box and Shift+click on another checkbox all the rows in between these rows should be checked. Ex: click on 2nd row and shift click on 8th row, all the rows in between 2nd and 8th should be selected.

The current FilterService does not handle nested composite filter descriptors, ignoring them and only processing individual filter descriptors. This limits functionality, especially for complex filtering scenarios. The request is to enhance FilterService to fully support and process nested composite filter descriptors.

Look at the notes for use cases.