The reusable Form XObject content always resets its GraphicState color property. Instead, it should take the current GraphicState color from the content stream. This may result in wrong colors.
The character is rendered with different glyph geometry and wrong glyph width which results in overlapping text.
The same property is available for MS TooltipService in WPF.
If you place a TextBlock in the QuickAccessToolbar and the Ofice_Black theme is applied you get black foreground on black background which makes the text unreadable. The content of the QAT must respect the theme applied to the RadRibbonView control.
Implement a mechanism that allows embedding font data when exporting documents.
ApplicationMenu do not have keyboard navigation - pressing arrows do not navigate thru the application menu items.
Declined as a duplicate of: https://feedback.telerik.com/wpf/1352753-ribbonview-applicationmenu-do-not-have-keyboard-navigation.
Add support for axis with multi-level categories
Declined as a duplicate of: https://feedback.telerik.com/wpf/1351027-chartview-add-support-for-axis-with-multi-level-categories
When you hit the Enter key and a number simultaneously the number is removed from the Value of the RadMaskedNumericInput Workaround: Handle the KeyDown event of the RadMaskedNumericInput control, when the Enter key is pressed. private void INPUT_KeyDown(object sender, KeyEventArgs e) { if (e.Key == Key.Enter) { if (INPUT.Value.ToString().Length > 0) { RadWindow.Alert(INPUT.Value.ToString()); } e.Handled = true; } }
The Gridview Distinct Filters can't be reuse if the filtering panel is close.
When the filter panel is reopen selecting or deselecting distinct filter have no effect.
This is reproductible in telerik demo in any gridview with distinct filter.
the bug is present in browser and oob applications.
RadMaps Silverlight BingMap provider stopped displaying tiles in 2022 due to change in Bing Maps service.
Check notes here:
https://docs.microsoft.com/en-us/answers/questions/799630/arcgis-map-services-stopped-loading.html
Either workaround or statement regarding the future of this feature is needed.