When having a DataGrid with DataPager and going on the second page, the DataGrid keyboard navigation does not work as expected. The keyboard navigation works only on the first page.

when changing property value programmatically, the row background style selector does not apply. You need to scroll the data or resize the control, then the change applies.

The selector works when editing the datagrid value trough the UI, but does not work when changing the value programmatically.

having a datagrid with columns and setting the celleditor style to text column, then setting SelectionOnFocus to some value, then enter the edit mode, for example select all or cursor at start do not apply., always cursor at end applies.

The behavior also happens when using CellEditTemplate and there is RadEntry in it. The SelectionOnFocus does not apply. 

when adding items to the collection bound to the datagrid ItemsSource, the empty template remains visible.

this was working with 11.1.0 version

Having a RadButton in a template/text column cell template and clicking on it, or hovering, at some point the text disappears when using the telerik theming

Workaround: 
Use the RadTemplatedButton: https://www.telerik.com/maui-ui/documentation/controls/templatedbutton/overview 

Provide an option to drag a cell content and drop it to another cell for both default and skia render modes

Makes this feature also available for skia cell renderer

I'd appreciate proper selector for this. I think that's a good addition for DataGrid customization having a style selector for the mouse hover based on the cell value

the following scenario: 2 property aggregate descriptors that use different properties than the property bound to the column and when editing the column, one of the property in the footer text does not update the value in the UI. 

The DataGrid is blank in when using AOT compilator

When RadDataGrid uses LoadOnDemand with a plain ObservableCollection<T> as its ItemsSource, there is no supported API for the application to indicate that no further items are available.

As a result, the grid can continue raising LoadOnDemand requests after the data source has returned all available items. Applications must currently maintain pagination state and use a custom LoadMoreData command or other workarounds to prevent additional requests.

Provide a supported option that allows applications to stop load-on-demand once no further data is available. The grid should resume requesting items when the relevant data/query state changes.