Won't Fix
Last Updated: 08 Dec 2020 11:03 by ADMIN
the issue could be reproduced when RadListView or RadDataGrid controls are inside the content of the accordion item
Won't Fix
Last Updated: 01 Oct 2020 11:42 by ADMIN
When you type in a symbol in the AutoComplete and the Popup that contains the available items appear, it is not possible to change its position(top/bottom of the AutoComplete) or change its template. This is problematic in scenarios where the AutoComplete is at the bottom of the view as it hides the software keyboard. 
Won't Fix
Last Updated: 28 Sep 2020 08:14 by ADMIN
Created by: Pavel R. Pavlov
Comments: 1
Category: AutoComplete
Type: Bug Report
When the suggestions get recycled, their text and image disappear.
Won't Fix
Last Updated: 13 Apr 2020 13:54 by ADMIN
If you place Editor or Entry inside a RadPopup control,  the editor's (entry's) feature of text selection to cut/copy/paste is not working for Android platform.
Won't Fix
Last Updated: 18 Oct 2019 12:40 by ADMIN
Created by: Tom
Comments: 1
Category: AutoCompleteView
Type: Bug Report
The virtual keyboard overlaps the component causing users to not see what they type.
Won't Fix
Last Updated: 29 Aug 2019 06:27 by ADMIN
Workaround for GroupHeaderTemplate:

        <Label Text="{Binding Group.Key}"/>

Workaround for column:

<telerikDataGrid:DataGridTemplateColumn HeaderText="Name" >
            <Label Text="{Binding Name}"/>

We have decided not to change the code of the RadDataGrid component in this regard. The root reason for this is the fact that the Skia APIs used to draw the text does not support automatic character fallback. To overcome this issue, people from Skia team have two suggestions. We have tested them out and none of them is applicable for the case of the DataGrid.
First approach slows down the performance of the component to a point where the DataGrid becomes unusable.
Second approach does not fix the problem in all cases.
Having this in mind the best approach for our customers in such cases is to use a TemplateCell with a Label inside it only for the column(s) where they expect symbols to occur. The Xamarin.Forms.Label supports automatic character fallback hence it should properly handle all cases.