If the value "-1" is passed in as one of the values in pageSizes input for the PagerPageSizesComponent, that option should be shown as "All" and should show all rows available for the grid.

Drag and Drop of grid's columns the same way we have on the jquery version (with a Input on the component saying if we want columns to be draggable)

Need to have Parent --> Child hierarchical records to be displayed in Grid..
It should support up to 'n' level , it means a parent can have any number of child records. can this be done using current Master Detail grids?.

 Parent 1
   --- Child 1
        -- Grand Child 1
            -- Grand Child 1
        -- Grand Child 2


Thanks in advance.

At current, if one wants to, (for example), highlight the entirety of a row, the natural choice would be to associate a background color with that row.  However, currently, this is not possible.  The closest we can come is to conditionally associate a given color with a div that happens to live in that cell, e.g.: 

<kendo-grid [data]="gridData" [height]="410">
            <kendo-grid-column field="ProductID" title="ID" width="40">
            </kendo-grid-column>
            <kendo-grid-column field="ProductName" title="Name" width="250">
            </kendo-grid-column>
            <kendo-grid-column field="Category.CategoryName" title="Category">
            </kendo-grid-column>
            <kendo-grid-column field="UnitPrice" title="Price" width="80">
              <ng-template kendoGridCellTemplate let-dataItem let-rowIndex="rowIndex">
               <div [class.myClass2]="dataItem.UnitPrice >= 20">{{dataItem.UnitPrice}}</div>
              </ng-template>
            </kendo-grid-column>
            <kendo-grid-column field="UnitsInStock" title="In stock" width="80">
            </kendo-grid-column>
            <kendo-grid-column field="Discontinued" title="Discontinued" width="120">
                <ng-template kendoGridCellTemplate let-dataItem>
                    <input type="checkbox" [checked]="dataItem.Discontinued" disabled/>
                </ng-template>
            </kendo-grid-column>
        </kendo-grid>

(where the class.myClass2 is defined as follows):

styles: [`
    .k-grid td {
      position: relative;
    }
      .myClass2 {
        background-color: rgba(255, 0, 0, 0.5);
        color: white;
        padding: 8px 12px;
        position: absolute;
        top: 0;
        left: 0;
        right: 0;
        bottom: 0;
        display: flex;
        align-items: center;
      }
    `]

But this doesn't reliably highlight a predictable amount of the cell, especially across browsers.

Thanks for your consideration,
  Jeff

The new Kendo for Angular Grid doesn't look to have any keyboard support. This is necessary to pass Section 508 a11y. I don't see any items on the Kendo github, nor any ideas in this portal. 

It would be great if grid component has option to filter date and numeric columns by range.

Same Feature as in Demo of JQuery: http://demos.telerik.com/kendo-ui/grid/column-resizing

Should emit an event with column sizes, so they could be stored in user settings.

Please add grid spinner configuration on grid, example <kendo-grid [loading]="true"></kendo-grid>

Angular 4x. version version of Grid must support all grid features we had in JQuery based version with Bootstrap CSS support.  

http://demos.telerik.com/kendo-ui/grid/index 

Any Plans for making grid or listview rows to be draggable

Need the ability to reorder columns and access the current configuration to store and load on next time user access the site.

Already exists on other products on the market and Kendo Grid for jQuery

http://demos.telerik.com/kendo-ui/grid/column-reordering

In Grid set Filter next Grid Column (http://demos.telerik.com/kendo-ui/grid/filter-menu-customization) like normal Kendo Grid Filter. 

We are seeing warning that <template> is deprecated and to use <ng-template> instead. Can this be addressed? Is the May release going to compatible with Angular 4?

Currently it seems that the columns widths are just divided up between the available width and the number of columns. Under that circumstance I am unable to specify a smaller width for a column. I would like for the column to adjust to the title at a minimum. Also it would be nice if we could drag the columns widths bigger or smaller.

provide main.js so I don't get kendo-angular-grid/dist/npm/js/main.js 404. Now how to get that file? Right no information anywhere.
At least primeng works so I can use that grid instead.

The behavior is inspired by the responsive utilities of Bootstrap: https://v4-alpha.getbootstrap.com/layout/responsive-utilities/ 

The column visibility feature may be implemented through the `visibleFrom` and `hiddenFrom` column properties. These allow columns to be shown / hidden based on the **viewport size**. For example,

```
    {
        visibleFrom: 1024, // show column on viewports bigger than or equal to 1024px
        hiddenFrom: 680 // hide column on viewports bigger than or equal to 680px
    }
```

We can cater for developers who use Bootstrap by providing presets, based on the Bootstrap 4 responsive monikers - https://v4-alpha.getbootstrap.com/layout/grid/#variables  (`xs` / `sm` / `md` / `lg` / `xl`). See the link for the default values.

```
    {
        visibleFrom: "md", // show column on medium-sized viewports (and above)
        hiddenFrom: "sm" // hide column on small-sized viewports (and above)
    }
```
The `visibleFrom` and `hiddenFrom` properties influence the default column visibility. The `visible` property overrides the default visibility -- columns declared as `visible: false`, show on every device, and columns with `visible: false` won't show at all. Notice that the `visible` property is 

The resize sensor component will be used to create the responsive pager, as the pager behavior is related to the grid width and not the viewport width.

Interoperability with the column menu (show/hide columns) can be achieved through the use of the `visible` property, to allow the default behavior to be overwritten. This raises problems when the application is switched between different screens, as the menu needs to work with a nullable boolean.

Option to export to CSV, Excel, etc.

Scrolling like this : http://legacy.datatables.net/release-datatables/examples/basic_init/scroll_y_infinite.html

Say you have 100.000+ rows of data.
With classic or virtual scrolling, you allow your user to go to the last page very easily. It ends up with huge skip parameter, and disastrous load times from the DB.

You don't want users to be able to run queries which are at the same time useless and very time-consuming server-side.

What you really want is for your user to be able to browse a bit of the data with fast queries, and if he wants something else, he should filter data.

Infinite scrolling gives him just that feeling.