When TabStopMode is set to "Skip" on all columns and you press Tab, RadGridView scrolls a little.

Workaround: define a custom KeyboardCommandProvider and clear the pending commands.

Clicking outside the dialog should hide it.

The problem should be resolved with lib version 2016.1.125

As a user I would like to have Unfocused state for selected GridViewCells when SelectionMode="Cell". 
Similar to the Unfocused state for selected GridViewRows (you can check this article as a reference: http://​www.telerik.com/help/wpf/gridview-selection-unfocused-state.html).

Enable multiple rows to be edited in a RadGridView at once.

We currently do this based on creating multiple row selection and editing the last selected cell and then applying the value (if valid to do so) across the selection.

The sort index will not be displayed when applying a custom sorting without adding a SortDescriptor, You can consider implementing Custom Sorting using the IComparable interface instead. As an example please refer to the Custom Sorting with IComparable WPF Demo. Using a generic SortDescriptor would also be an option. 
Please check our online documentation for a further reference: http://docs.telerik.com/devtools/wpf/controls/radgridview/sorting/custom

It does not matter if the button is in a CellTemplate, CellEditTemplate, ControlPanelItem etc.

1. Set RadGridView's setting DragElementAction="ExtendedSelect". 
2. Open a window on selecting a row.
3. Close the window, the RadGridView becomes ExtendedSelect.

Note: Most probably this problem is actually caused by a limitation in the Silverlight platform. Once a Window is shown, there is no way to detect that the mouse is released.

1. Define a custom AggregateFunction for a column
2. Group on a column
3. A calculation on the AggregateFunction is invoked
3. The Grouping.Key (of the input parameter) corresponds to the correct key
4. Edit a value on the column (having the AggregateFunction)
5. A calculation is invoked, but the Grouping.Key is "1" and not the correct key.

MergedCellsStyle and MergedCellsStyleSelector properties will be available with Q2 2016.

Right now, if you programmatically increase the RadGridView's font size, the columns get bigger to accommodate. So far, so good. But if you then make the font size smaller, the columns stay the same large-font width. 

Further, double-clicking the gridsplitter that separates the columns after the above procedure doesn't resize the column like it would if you'd manually resized the column and then double-clicking the gridsplitter - instead, nothing happens.

Finally, it would be nice to have a programmatic interface to autosize the columns, something like

MyGrid.Columns(0).AutoSize()

Thanks!

Dear Telerik Support Team,

I am encountering an issue with the RadGridView control in my application, which is impacting the usability for users relying on screen readers. Below, I have outlined the details of my development environment, the problem, and attached a sample project demonstrating the issue.

Issue Description:
In the attached sample project, I have implemented a simple RadGridView without any custom styling and populated it with sample data. I have observed that the focus behavior is inconsistent, particularly with the first cell in the RadGridView. When attempting to focus the first cell, only the cell itself receives focus, unlike subsequent cells where both the cell and the entire row are focused. This inconsistency results in screen readers failing to read out the content of the first cell, while they correctly read the contents of all other cells.

Upon further investigation using the Snoop utility to explore the visual tree, I noticed that the GotFocused event for the initially focused cell identifies it as being of type RadGridView, whereas, for other cells, the type is GridViewCell. This discrepancy seems to be at the root of the issue.

Attachments:
I have included a simplified, runnable standalone application that reproduces this behavior. Please find the sample project attached to this ticket.

I believe this might be a bug affecting the accessibility of the application, and I would greatly appreciate your guidance on whether this is a known issue with a workaround or if there's a fix available.

Thank you for your assistance.

Best regards,

Christian

First Tab:

Second Tab: