Hallo,

i want to Render PDF Files with the PDF Viewer Component.

The Data of the PDF is already fetched from the API when the PDF-Viewer starts Rendering the Loading animation appears and freezes.

After a few Seconds the PDF will be Rendered.

The size of the PDF File is about 5MB.

 

 

If you compare the print quality against the Kendo UI jQuery PDF viewer, the quality difference is night and day. We did not investigate what is happening under the hood in both components. However, the same printing dialog appears when printing via both components and both of them are web components, which indicates to us, that this issue is not related to the browser.

I am opening a standard PDF document and it is not properly displayed in the PDF Viewer. For example, you can see the logo and the table borders but the text of the PDF is missing. If you open the same document in a normal Adobe viewer it is fine.

If the PdfViewer is initialized with a default document, the display performance of this document will be a lot worse, compared to PDF documents that are loaded programmatically after the component is already on the web page.

 

When you search for a term, the document is not scrolled. Also when the user inserts a search term and clicks Enter the document is scrolled to the second match instead of the first one.

Open a PDF file in the PDF Viewer. Tap the magnifier icon to initiate the search. Start typing, the component freezes. 

The loading animation is visible only when a user opens a file from the Toolbar of the component. When programmatically opening a file, the loader is not shown. 

 

I want to set the Data of a PDFViewer from the OnRowClick event handler. If I use the ReadAllBytesAsync() method, the PDF viewer does not render the PDF document. I need to use the synchronous version (ReadAllBytes) to make this work.

Open the PDF Viewer component online demo and click the download button:

Expected - the PDF must be downloaded.

Current - the file is not downloaded.

Set the PdfViewer document (data) value to null. As a result, an endless loader will appear.

===

ADMIN EDIT

===

A possible workaround for the time being is to re-initialize the component after clearing the file: https://blazorrepl.telerik.com/cHYwQola24zzBOAd02.