Please provide row virtualization as addition to the current virtual scrolling functionality.

Current behavior
Virtual scrolling is currently tied to the pageSize. This is not always desirable as page size can be much higher than the visible area to optimise for network latency.

For example if the pageSize is 200 rows and the grid is only 10 rows high we'll be rendering 190 more rows than needed at initialization time.

Expected behavior
Virtual scrolling should include an option to render only the visible rows at any given time.

The sticky columns functionality is not working properly with multi-column headers (kendo-grid-column-group).

It would be a nice enhancement to provide support for such scenarios and perform the necessary internal calculations. That will ensure locking a group column will be working as expected.

Example of the current behavior - https://stackblitz.com/edit/angular-y2dtxq

Hi Team,

It would be nice to have a feature that allows the developer to customize the Grid PDF export loading indicator like the kendoGridLoadingTemplate.

Thank you for your consideration.

Change the position of the grid filter dropdown, so it is unclear for which column it applies when opened. For example, as seen in the below screenshots, the popup of the filter to be displayed under the column to which it applies instead of on the right-hand side of it.

Actual behavior:

Desired behavior:

Related ticked: 1562369

Hi,

Please provide an option that allows disabling the Clear button located in the Grid filter menu. Currently, it is always enabled, but I expect that it should be enabled only when there is a filter applied for the specific column that can be cleared. The required behavior is similar to the way the Filter button in the filter menu is functioning.

thanks

Hi team,

It will be a good addition if there was an option for a different drag selection similar to the Excel cell selection. For example, check the attached gif.

Thank you for your consideration.

Hi,

Please provide an option to use the classic Calendar instead of the Infinity (used by default) when using Grid filtering.

thanks

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>

Please provide a how-to example that demonstrates how to move from one cell to the other using "Tab" in an editable Grid with virtual columns.

When there are more columns than are visible within the viewport the columns are virtualized which is expected.

However, when editing a row and we want to tab through the fields, we can only tab through the fields that are in the viewport and once we tab from the last viewport field our focus leaves the grid entirely and we cannot navigate to the remaining fields at all.

Thank you.

Hi,

It will be an excellent enhancement to the Grid component if cell mouse enter/leave events are added, providing the dataItem(other information like rowIndex and columnIndex might also be useful) on the current hovered cell.

Thank you for your consideration.

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.

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/

Current behavior

The developer must measure the Grid row height in the browser and set it to the `rowHeight` in order for virtual scrolling to work correctly. Setting an incorrect value can lead to subtle errors - glitches during scrolling or inability to scroll down to the last row.

The row height may change as a result of a styling adjustments and is not guaranteed to be identical across browsers and devices. This makes the current workflow tedious and error-prone.

One of the following approaches can be used to solve this issue:

• The Grid should take accurate measurements of the row height at run-time. The developer should still be aware that row height is constant . This is the preferred approach as it does not change current behavior, instead the set `rowHeight` value is ignored.
• The set `rowHeight` should be applied as inline styles. This is a more risky approach as it will change the appearance of the Grid.
  

Overcoming the last listed limitation would be nice:

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

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/

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

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

Hi Kendo Angular team,

It will be a nice improvement if there is an option to set a specific type for the Grid data item and the templates. This will allow checking the types inside the templates when fullTemplateTypeCheck is on.