Hi Team,

I would like to request a new event for the Kendo UI Grid which will determine when the Grid has been resized in height.  Right now, I have created a custom directive which uses the changeNotification property to handle when the scrollbar is shown.  But it would be nice if there was something built in.

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,

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 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/

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 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.

When the column filter is set to date, it shows a built-in filter menu with the DatePicker and the operators dropdown. Can we have a similar feature where the filter Menu shows the DateTimePicker with the operators and logic dropdown?

I have a groupable kendo grid. I'm utilizing the kendoGridGroupHeaderColumnTemplate directive.

I see that <kendo-grid-column> takes headerClass and headerStyle, but neither applies styles to the grouped header.

Please provide a groupedHeaderClass and groupHeaderStyle properties so that I can style the cell rendered by kendoGridGroupHeaderColumnTemplate.

Thanks,

-Adam

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

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>

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, we can specify which columns to be included in the exported PDF file or Excel file:

https://www.telerik.com/kendo-angular-ui/components/grid/export/pdf-export/#toc-customizing-exported-columns

It would be also convenient to have a property such as excludeFromPDF (or similar) for scenarios when only a single column should be removed from the PDF file.

Right now this is possible but defining the rest of the columns between <kendo-grid-pdf> tags which in scenarios with more columns drastically increases the HTML template.