Workaround: set UseCompatibleTextRendering to true.
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.
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:
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).
The Telerik PDF viewer should correctly honor and render the stroke-width
property defined within SVG elements embedded in the PDF file.
All strokes in SVGs appear very thin, with no visual difference despite varying stroke widths in the source SVG.
_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.Component | Version |
---|---|
Telerik UI | 2025.1.211.48 |
.NET Framework | .NET Framework 4.8 |
OS | Windows 11 |
Ensure that the rendering engine used by RadPdfViewer
fully supports the SVG stroke-width
attribute when parsing and rendering embedded SVG content.
Visual Studio 2022 crashes when working with a solution containing two WinForms projects:
Steps to Reproduce:
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:
Additional Notes:
For example, if you choose to print second page like this:
It prints only the first page of the document, instead of the second page.
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.
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
RadMessageBox(form) is a telerik replacement for the System.Windows.Forms.MessageBox.
MessageBox has a parameter MessageBoxOptions.DefaultDesktopOnly which makes it (surprisingly) topmost. RadMessageBox does not have this option.
I have a scenario where the RadMessageBox is hidden by a total different application when shown. So I need to make it topmost.
Can you add some kind op RadMessageBoxOptions to make it topmost?
The EnableHotTracking property works only in the first level hierarchy. The lower levels still get highlighted.