In the following scenario, we have enabled the pager functionality of the control. If we move to a different page and then set the DataSource to Null, the page index will not be reset. 

The search functionality is inconsistent in Unbound Mode. Typing a word highlights all rows that contain that word or string, as expected. However, if the cursor is moved and additional characters are typed at the beginning of the search box, no results are returned, even if matching rows exist that contain the updated string combination.

The same behavior is not observed in bound mode.

In this case, we have a GridViewHyperlinkColumn in which we have a cell with an empty string or null value. Exporting the control in XLSX format leads to an exception.

In this scenario, the MultiSelect option of the control is enabled. If we click and hold the mouse to select multiple cells and go over a merged cell, NullReferenceException is thrown.

The control allows you to scroll the view while dragging and appointment. In a case when the appointment is at the bottom of the view and we try to move it above, the view will scroll to see the top cells. When the mouse is above the column header cells, the scroll stops. This could be improved.

When I show some text and set IsWordWrapEnabled to true... the horizontalscrollbar disappears


but when I set IsWordWrapEnabled to false after this, the horizontalscrollbar does not appear 

in your code I saw this:

                ScrollBarVisibility newScrollVisibility = editor.IsWordWrapEnabled ? ScrollBarVisibility.Disabled : ScrollBarVisibility.Auto;
                editor.SetValue(HorizontalScrollBarVisibilityProperty, newScrollVisibility);

But this .Auto property doesn't seem te work. 
Further more, next to this problem, I'd like to set this horizontalscrollbar to appear and disappear depending on the text width...
but I'm afraid this would be depending on the .auto property

 

When the RadPropertyGrid is in group scenario and we expand more property items, the scroll value is incorrect. 

 

Open the "First Look" demo app for rich text editor. Delete all the text. Insert a table with 5 columns and 2 rows. Select first 2 columns (4 cells in total). Merge these cells. The merged cell should have the width of 2 normal columns. Save this document as RTF. Open the document. The width of all columns is wrong. The merged cell now is wide as one normal column.

It seems that two issues are combined into one problem. First, two merged columns are converted into one column. If I try to split the merged cell before the save I get my two columns back, but after the save there are only two rows after the split, but only one column. Second, the "AutoFit to Window" option is messing with the column widths. If I set the table to "Fixed Column Width" then the table remains unchanged after reload. But this option doesn't work if the merged cell is selected. Must unselect it first, or change the option before the merge. But this minor annoyance is not the part of this bug report.

Hello team!

I've found a misbehavior on RadForm when setting the size.

When you set the Size of the Form before it actually has shown then it will do some re-calculation, change the form size several times, and ending up in a too big size. The behavior is different to a original Form and that's why I'd treat this as bug.

The first screenshot shows a RadForm that set itself to ClientSize = 500; 500 on the constructor, like usual. It ends up in a size slightly bigger then defined.


This second screenshot shows a RadForm that set itself to ClientSize on "Shown". It ends up in having the correct size.

Whenever you set a breakpoint to the method "Form1_Resize" you can capture that the first time the Size of the RadForm get changed is our "ClientSize = new Size(500, 500)". Then the Size get changed two times by RadForm itself to something slightly smaller. Lastly the Size get changed by RadForm another time, but this time slightly bigger

This behaviors can lead to inconsistent UI size, e. .g small spaces when using AutoSize = true in certain cases. But yet didn't figured completely out when exactly it happens, just that it comes from this slightly increased Size of RadForm.

Can you please take a look to it and, if it is one, report it as bug?

Thank you very much!

Regards,
Pascal

How to reproduce: set the Size property of the form in the designer of Visual Studio, pay attention to the serialized ClientSize value. Run the form and check the ClientSize, it has increased

Workaround: 
public partial class Form2 : RadForm
{
    public Form2()
    {
        InitializeComponent();
        Padding p = TelerikDpiHelper.ScalePadding(this.FormBehavior.ClientMargin, new SizeF(1f / this.RootElement.DpiScaleFactor.Width, 1f / this.RootElement.DpiScaleFactor.Height));
        this.MaximumSize = new Size(this.Size.Width - p.Horizontal, this.Size.Height - p.Vertical- this.FormBehavior.ClientMargin.Bottom + this.FormElement.TitleBar.Size.Height);
    }

    protected override void OnShown(EventArgs e)
    {
        base.OnShown(e);

        this.MaximumSize = new Size(0, 0);
    }
}

Good morning,

when I open a mdi child form from another child form and change WindowState from Minimize to Normal the form is not shown with correct size.

When trying to open the QuickStart solution from 

C:\Program Files (x86)\Progress\Telerik UI for WinForms 2025 Q1\Examples

installation folder, the following error appears:

In this scenario, the scrollbars are shown on an empty document when the form is moved to HDPI monitor.

Overview

This repository documents a bug found in the Telerik PDF Viewer control for Windows Forms. The issue specifically affects the rendering of SVG graphics embedded in PDF files, where the stroke-width attribute is ignored by the viewer.

Affected Component

• Product: Telerik UI for WinForms
• Control: `RadPdfViewer'
• Version: 2025.01
• Platform: Windows Forms (.NET Framework)

Description of the Issue

When a PDF file contains an embedded SVG graphic that utilizes the stroke-width CSS property (or SVG attribute), the stroke width is not rendered correctly in Telerik's PDF preview control. Regardless of:

• Unit used (e.g., px, pt, em, %, etc.)
• Value assigned (e.g., stroke-width: 5, stroke-width: 30, etc.)

…the resulting line always appears thin, as if the stroke width were ignored entirely. This makes the SVG appear incorrectly and inconsistent with its rendering in other PDF viewers (e.g., Adobe Acrobat, Chrome's built-in viewer).

Steps to Reproduce

1. Run the application from provided MCVE
2. Observe the SVG lines in PDF preview: all strokes appear thin, regardless of defined stroke width.

Expected Behavior

The Telerik PDF viewer should correctly honor and render the stroke-width property defined within SVG elements embedded in the PDF file.

Actual Behavior

All strokes in SVGs appear very thin, with no visual difference despite varying stroke widths in the source SVG.

Sample Files

• ✅ _PdfExample.pdf: A PDF with SVG lines that render correctly in Microsoft Edge.
• ✅ _PdfExample.pdf: Screenshot of how the PDF file looks in Microsoft Edge.
• ❌ _ScreenshotFromTelerik.png: Screenshot of how the same file looks in the Telerik PDF Viewer (note the thin lines).
• 🔍 _LargeStroke.svg, _SmallStroke.svg: The original SVGs used in the PDF file.

Environment

Component	Version
Telerik UI	2025.1.211.48
.NET Framework	.NET Framework 4.8
OS	Windows 11

Suggested Fix

Ensure that the rendering engine used by RadPdfViewer fully supports the SVG stroke-width attribute when parsing and rendering embedded SVG content.

Workaround: set UseCompatibleTextRendering to true.

Visual Studio 2022 crashes when working with a solution containing two WinForms projects:

• Project 1: WinForms (.NET 9) with Telerik
• Project 2: WinForms (.NET 6) without Telerik

Steps to Reproduce:

1. Create a new solution in Visual Studio 2022.
2. Add two WinForms projects:
   • Project 1: WinForms (.NET 9) with Telerik
   • Project 2: WinForms (.NET 6) without Telerik
3. Open the WinForms designer for a form in Project 1 (Telerik, .NET 9).
4. Without closing the designer, open the WinForms designer for a form in Project 2 (.NET 6, no Telerik).
5. Switch to the code view of the form in Project 2.
6. Switch back to the WinForms designer in Project 2.

Expected Result:
Visual Studio should smoothly switch between code and designer views without issues.

Actual Result:
Visual Studio freezes and crashes after switching back to the WinForms designer in Project 2.

Environment:

• Visual Studio 2022
• Windows Version: (Windows 11 x64)
• Telerik WinForms Version: (2025.1.211)

Additional Notes:

• The issue seems to be related to handling different .NET versions and Telerik components in the same solution.
• The crash occurs consistently when following the steps above.
• No explicit error messages are shown before Visual Studio closes.

---

This behavior is related to how the control is measured while using the MS Form. In the given scenario, the control has many columns, and some of them are pinned. Moving to the last column and typing in the filter cell will filter the rows in the column. However, when filtering, if the row number is less than the viewport, the vertical scrollbar will disappear as it is not needed anymore, and the filter editor will be placed in the wrong column. This will mess with the filter cell editor. 

In the current scenario, when clicking on the checkbox inside a GridViewCheckBoxColumn, the CellBeginEdit event will be called. If we cancel the event by setting the Cancel property to true, the CellBeginEdit will be called twice.

ImageKey is cleared when moving a node from one treeview to another and disposing the first.