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.

Requested for Kendo UI originally, seems to be common scenario:

http://www.telerik.com/forums/automatically-hide-a-column-when-a-user-drags-it-up-to-be-a-group-header

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.

hi guys,
We are debating between ag-grid for Kendo ui angular 2....what better to use?
1. Does Kendo UI grid supports RTL (Right To Left)?
2.How to implement expandable row In ag grid angular 2 ?
3. How to implement paging  In ag grid angular 2

Angular 2 - type script 

Hi guys,
Does Kendo UI grid supports RTL (Right To Left)?

If not, does it going to be implemented on January 18th?

10X

Like kendo ui jquery. 

Add events like detailInit, detailExpand, detailCollapse in the Kendo Grid for jQuery. Add possibility to know whether the detail template is expanded or not.

Presently, when I place a bootstrap drop-down inside a cell the drop down is cropped when open (it is hidden behind the rows below). 

Can you please endeavor to eradicate this issue within your components so that we don't have to jump through lots of "css hoops" or worse "write jquery to do it" in order to get the desired result. 

Your components should be fully compatible with bootstrap (since you have a BS theme and lets face it, its pretty well industry standard these days)

Many of our "grids" require an Action column which in some cases has more buttons than we would like to put "side-by-side" and so the best option is to add a drop-down action button to hold the action commands.

At present there is no equivalent Kendo component that will do this for us either. Your grid cells should really cater for this as other users may want a custom column with "drop down" content too.

MultiColumn Headers Support like in Kendo UI Grid

At the moment, the selected row is not cleared when the data changes (or we change the page). There is no way to clear the selection in the grid, which would be useful when 1 data from a grid depends on the selection from the parent grid.
Having an API to change the selected row, would help.

Currently KendoUI supports responsiveness (http://demos.telerik.com/kendo-ui/responsive/) Ideally all Angular 2 controls should behave in same way, this would allow creating pages that work nicely on desktop, tablets and mobile.  

Just like KendoUI supports offline datasource sync.

We would like to have the possibilty to create custom implementation of grid columns (or any other control/component). Because we also have this in our WPF projects and it was very useful to minimize the redundant code and also the "initialization code". This can't be done in a simple template, for example we need to inject services and get data etc..

Example:
In our WPF project have lots of different grids with values related to units. The cell can convert this unit to and other unit itself, it can localize the texts, it shows the information in some kind of "progress bar", has a tooltip, etc... And all we have to do in the code is to set a column like this <custom-column valueField="test" unitField="test2" />.

It would be great to have this feature in the Angular 2 grid as well.

Hi ,

I would like to vote for this .