If the Chrome browser zoom is different from 100%, it is not possible to reorder the RadGrid columns.

The problem can be reproduced at https://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/columns/column-row-resize-reorder/defaultcs.aspx .

Enable filtering, Enable HeaderContextMenu and HeaderContextMenuFilter.

First, filter using the HeaderContextMenu filter (e.g. OrderDate GreaterThanOrEqualTo "someDate" AND OrderDate LessThanOrEqualTo "someOtherDate"

Second, apply a filter on another column using the Header filter only (e.g. Freight GreaterThanOrEqualTo "4")

At this point, the filtering applied by the HeaderContexFilterMenu is now partially removed.

Issue only appears when Header filter and HeaderContextMenu filter are used in combination. They work as expected when used separately.

How is it possible to autofit / autosize a giving column (or all columns) when exporting the contents from RadGrid to xlsx using ExportStructure?

The only option available is Width with a defined value. I was unable to find an autofit / autosize function.

And also add AutoFilter feature...

Please consider to add this features :-)

There are two possible approaches to overcome this issue:
- First approach would be to get a reference to the GridHTMLEditorColumn and add the desired tools in the code behind using the "OnItemCreated" server event handler of RadGrid.
- Second approach would be to use GridTemplateColumn with RadEditor.

I have a RadGrid with around 150 columns and a few hundred rows. Currently, I'm looping over them and setting their widths with the resizeColumn function. Unfortunately, it's triggering a recalculation of the layout every time I call this function, so the total page load time can be in the minutes.

Oddly, much of the time was spent on the line:
e.style.width=e.offsetWidth-d+"px";

Chrome's developer tools helpfully pointed me at Forced Reflow. Apparently, when a width is set, initially no extra work is done. When another width is requested, the previous width may have changed it, so the whole layout gets recalculated.

The feature I'd like to request is a function to set column widths in bulk (accepting anything like an array or a dictionary would be fine) that doesn't trigger this recalculation mid-function.

The date pickers default to the year 1999 and do not accept inputs, so you cannot filter GridDateTimeColumn instances through the header context menu or the excel-like filtering. The standard filter item and range filter can still be used instead of context menus, but they are not available with excel-like filtering.

At the moment, RTL support for excel like filtering is not implemented. It displays the following issues

    - menu position is wrong (tends to show up on the column to the left)
    - controls alignment inside the menu is wrong (ltr)

You can find attached a sample and screenshots with the current behavior

Alternating Row style of RadGrid is not applied when using Bootstrap skin.

Steps to reproduce:
For all other Skins these approaches work:
        div.RadGrid tr.rgAltRow {
            background-color: aqua;
        }

Or:
 <AlternatingItemStyle BackColor="Aqua" />

The reason probably is because there is >td directive built-in, which needs to be overridden manually in order for the styling to take effect (this works):
        div.RadGrid tr.rgAltRow > td {
            background-color: aqua;
        }


A possible workaround for this issue is available in the following forum post:
https://www.telerik.com/forums/alternatingitemstyle-5e16887f3085#odVQBomUikiIJfrxeBQrww

The reason for the behavior is that the column editor does not move to the cell when you cancel its opening. Opening a cell in the same column expects the column editor to be in the previously opened cell, however, and this causes the error. Repro is attached to illustrate the scenario.

Workarounds:
- Use EditType=Cell so that each cell opens independently of the row (wokaround 1).
- Use the provided function override (workaround 2). Make sure to remove it after upgrading to a release that has the fix. This function override may prevent you from getting other updates and fixes in this function.
- Use a template column and hide the editor based on your condition in the OnBatchEditOpened event (workaround 3)

For keyboard users who don't have a specific Context Menu key (see  https://en.wikipedia.org/wiki/Menu_key), they typically need to use the Windows standard SHIFT+F10 hotkey to trigger a contextmenu event.

For example:

1.	In IE, load http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/columns/context-menu/defaultcs.aspx
2.	Tab to a column header link
3.	Press SHIFT+F10 (standard Windows/IE hotkey to open context menu)
4.	Notice the context menu displays, however, the focus is really on the IE menubar. IE supports F10 to open the menubar, but is also seeing SHIFT+F10 too.

Or
1.	In FireFox, load http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/columns/context-menu/defaultcs.aspx
2.	Tab to a column header link
3.	Press SHIFT+F10 (standard Windows/IE hotkey to open context menu) then press down arrow
4.	Notice the context menu displays, however, the focus is really on FireFox's application system menu in the upper left.

Chrome does not have this issue - it opens the grid context menu only.
We need IE and FireFox to also only open the grid's context menu, and not trigger default browser behavior.

According to https://yuilibrary.com/yui/docs/event/contextmenu.html, it is possible to correct this behavior by calling event.preventDefault() when SHIFT+F10 is pressed, but then trigger a synthetic contextmenu event anyway.

As a workaround, we know users can press Escape to close the browser's default menu and bring focus back into the HTML document (and thus the grid's context menu), but this throws off the user experience and becomes a training issue.

If there are hidden columns before the ColumnGroups while exporting to excel (format Xlsx), header text of columngroups are shifted to the left.

 - Workaround, is to move the hidden column after the ColumnGroups.

In some cases, inside the Grid table, the tfoot element is rendered before the tbody element. This causes some readers to read the footer before the body. 

A possible workaround is moving the tfoot after the tbody in the OnGridCreated event:

<script>
function OnGridCreated(sender, args) {
    var $ = $telerik.$;
    $('tfoot').each(function (index, item) {
        var $item = $(item);
        var $next = $item.next();
        if ($next[0]) {
            if ($next[0].tagName.toLowerCase() == "tbody") {
                 $item.insertAfter($next);
            }
        }
    });
}
</script>

 
A forum discussion on the topic: 
Any way to change the order in which RadGrid renders THEAD, TBODY, and TFOOT?
 

I think it would be a great addition to the grid control if there was an attribute that you could apply to the columns called "SortNullsLast" or something along those lines. This attribute would modify the grid's sorting functionality and only apply the ascending or descending sort to non-null values.

Currently when you sort ascending, null values are sorted to the top of the grid. This new attribute would allow the non-null values to show up at the top in ascending order.

An example of why this would be useful is having a grid that tracks an optional requested completion date of a task. You would want to be able to sort the grid so that the earliest date shows first in the grid. Right now, any records that don't have this optional date would show first, which doesn't make sense.

Auto-Fit column width when exporting to excel using Format="Xlsx"

 I'd really like to have the columns automatically adjust to fit the width of the content.

A workaround is to take the header border color and set it to all rows 

- Default skin
           .RadGrid_Default .rgRow > td,
            .RadGrid_Default .rgAltRow > td {
                border-left-color: rgb(130, 130, 130);
            }


- BlackMetroTouch skin

            .RadGrid_BlackMetroTouch .rgRow > td,
            .RadGrid_BlackMetroTouch .rgAltRow > td {
                border-left-color: rgb(51, 51, 51);
            }

            .RadGrid_BlackMetroTouch .rgRow > td,
            .RadGrid_BlackMetroTouch .rgAltRow > td {
                border-bottom-width: 0px; /*remove extra space between rows that becomes visible when you put on borders for alt rows*/
            }


- WebBlue skin

            .RadGrid_WebBlue .rgRow > td,
            .RadGrid_WebBlue .rgAltRow > td
            {
                border-left-color: rgb(69, 95, 119);
            }

As shown in the attached screen, please keep the column headers Fixed or Visible so they are still visible when users scroll down to see the other data, for both RadGrid and PivotGrid:

It seems the element somehow considmes the scrolling/touch action and the grid does not scroll unless you hit the gap where the custom element does not reach.

A workaround is to enforce overflow: auto to the scrollable element of the grid. A sample is attached below.

        div.rgDataDiv {
            overflow: auto !important;
        }

Provide a simple interface to showcase exactly in what order the columns have been sorted in (ex. 1, 2, 3, etc in column header) - matching the functionality in Kendo UI Grid:

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

I would like to suggest that the Buttons in the RadGrid allow databinding to the CommandName and CommandArgument fields.  And pretty much all the buttons or anything that triggers an ItemCommand event that allow a CommandName and CommandArgument have their properties to be databound and accessible in the code behind.

Thanks!!!