We have a feature where we initialize our Grids with row filters, but we don't display them right away. We show hide them with a "Show/Hide Filters" button. It would be great to save some time on initial load of the grid (our client wants the ability to display up to ~100 columns with filters, and there's a noticeable performance impact building those filter controls), and delay that time for if/when the user decides they want to actually use the filters.

We have a project where we need the infinite scroll, column sorting/filtering, and remote data enabled.  We are having some issues with sort and filter.  For quick reference, I used the grid demo and changed it to reflect our configuration.  The problem is the grid fires the read command twice when we have loaded more than one page of data. No issues when we have only loaded the first page.

https://dojo.telerik.com/UDoREFID

To reproduce:

1.  Open Chrome

2.  Load the page

3. Hit run

4. Open Developer Tool

5. Switch to the Network tab and filter by XHR only  

7. Click ProductName to sort. There is only one AJAX call.

8. Scroll to the bottom so it loads the next page. It made two AJAX calls

Hi,

Currently the Selection & Export functionality does not automatically scroll down/up the Grid when the user tries to select cells that fall out of the view. Would be great if we have an option to allow automatic scroll and provide ability to choose additional cells (as in excel). Additional details are in 1576704.

We are extensively using this selection feature and the above mentioned behavior would save lot of our time and add value to the functionality.

Appreciate your support on this.

Thanks,

Raj

The loading indicator is not showing when the height property of a grid is not set.

Enable on-the-fly changes of selectable (selection mode) in the Grid widget

there are ready to use methods fadeIn & fadeOut for animation In jQuery. Kendo UI Window already uses nifty close-effect, how about implementing this behavior for a grid-control. Expanding/Colapsing Detail-Gird in Hierarchy will go smoothly and comply with other controls' animation.

The grid editable confirmation(delete alert) only popup jQuery alert currently, I want custom the dialog box style with window widget~

On updating the dataItem of a master row using the Observable "set()", the master row will repaint itself. However it also collapses the expanded detail row. The detail row can be expanded programmatically but this is clunky: the detail row flashes briefly while it collapses then immediately re-expands

The default behaviour should be to leave the row expanded.

Currently yo keep the selected row after refresh one needs to store the data first and then loop through all the rows to find it and select it again.
This is because the uid changes after refresh.
This does not work very well with large number of rows.
It would be great to have a setting that allowed the selected rows or cells to be kept after the refresh.

I like what FooTable.js does with a html table.  (hide fields based on breakpoints) and place them so that they are available via click on +

When a grid is first showed with a group value (e.g. a date value), it should be possible to apply a sorting direction to the grouped value (e.g. descending)

When performing Edit on a real-time grid, hide edit button to prevent simultaneous editing and data overwrite. 

There was a similar solution previous to signalR integration, http://www.telerik.com/forums/using-kendoui-grid-with-signalr#-3DZMT4HHE-rOWdEf_1mgQ

But with SignalR enabled grid, this could all be  built-in.

In your article: http://www.telerik.com/forums/how-to-make-a-non-editable-column-field, many developers make the point that the read-only attribute of a column should be part of the view, not model/data.
By not providing a column property to prevent editing, you have put the view logic in the wrong place.
Solution: Create a read-only property to each column to prevent editing.

<pre>
Kendoui grid date filterable "Is equal to" - Make it have a range base on what is input

If you have a date column in a grid and you filter it
and select "Is equal to"
it currently doesn't work very good unless your dates/time
are all on 12:00:00.000 AM

Maybe you could make the filter do this when "Is equal to"

If you select or inputput:

2/22/2004
	It will find the following rows:
	02/22/2004 00:00:00.000 <= datesFound < 02/23/2004 00:00:00.000

2/22/2004 06:
	It will find the following rows:
	02/22/2004 06:00:00.000 <= datesFound < 02/23/2004 07:00:00.000

2/22/2004 06:50
	It will find the following rows:
	02/22/2004 06:50:00.000 <= datesFound < 02/23/2004 07:51:00.000

2/22/2004 06:50:20
	It will find the following rows:
	02/22/2004 06:50:20.000 <= datesFound < 02/23/2004 07:51:21.000

2/22/2004 06:50:20.034
	It will find the following rows:
	02/22/2004 06:50:20.034 <= datesFound < 02/23/2004 07:51:21.035

Maybe have a toggle for (0-12 AM/PM) or (00-23 24 hour clock)
in the datetimepicker with a default setting that can be configured.

Maybe make the datetimepicker have a range for each 
Hour, minute, second, millisecond, AM/PM
* or blank - could act like a regular expression but would need to have the
    higher unit set. IE: (

		06:50:20.035   , 06:50:20.*   , 06:50:*.*   , 06:*:*.*   , *:*:*.*
			or
		 6:50:20.035 AM,  6:50:20.* AM,  6:50:*.* AM,  6:*:*.* AM, *:*:*.* *

		Not this:
			*:50:*.* *
	).

HH     ,        MM    , ss    , fff
00-23;*,        0-59;*, 0-59;*, 000 - 999;*

	or

H      , tt     , MM    , ss    , fff
0-12;* , AM/PM;*, 0-59;*, 0-59;*, 000 - 999;*

The yyyy,MM,dd could also be done this way so you could get all the rows
for a yyyy****, yyyyMM**, yyyyMMdd

</pre>

One should be able to cancel the detail expand or collapse events of the grids by providing a Expanding / Collapsing event.

One use case for this that would be way easier to implement is when one is using a detail template to edit some form of data related to the expanded row but not bound to it's data item, instead bound to specific data coming from other source.

If when you expand another row the previously expanded one gets collapsed I would like to be able to prevent that on those events to check for changes, challenge the user and act accordingly.

Currently the grid only includes row virtualization.
Column virtualization would be really beneficial for projects that display many columns

While it is currently possible to do this in JavaScript, it would be nice to have the functionality integrated into the Grid filter row.

For example,

columns.Bound(c => c.Title).Title("Title")
.HeaderHtmlAttributes(new { style = "text-align: center;" })
.Filterable(f => f.Cell(fc => fc
    .ShowOperators(false)
    .Operator("Contains")
    .Template("fnFilterAsYouType")
    .Placeholder("Title")
));

When performing a grid refresh, the grid re-renders the all the grid rows. 
I think it would be very efficient to have a choice to render specific, changed rows. 
This is valuable if the grid has many items (200 items for example).

Frozen Columns is a really useful addition to the grid, but we're not able to implement it at present as we don't want to force our users to always have one column locked.  We don't want to dictate which column that should be, e.g. fixing the LH column.  

If we could enable Frozen Columns giving the user freedom to freeze one or more columns of their choice, that would be ideal. 

The grid "beforeEdit" event is designed, as per documentation, "for preventing the editing depending on custom logic".

However, this event provides only information about the edited row, not cell, which severely limits what that logic can do.

A related event, "edit", passes information about the container, which is a table cell in incell mode. There is no reason for "beforeEdit" not to do the same - both event are triggered merely several lines apart.