When the user scrolls the PDF Viewer down and then opens another PDF file, the new document should display on the first page. Currently, the new file displays scrolled to the page from the previous file and the user must scroll to the top manually.

===

A possible workaround is to scroll the PDF file with JavaScript in the PDF Viewer OnOpen event:

@inject IJSRuntime js

<TelerikPdfViewer Data="@PdfSource"
                  Height="600px"
                  OnOpen="@OnPdfViewerOpen"
                  Class="@PdfViewerClass">
</TelerikPdfViewer>

<script suppress-error="BL9992">
    function scrollPdfToTop(selector) {
        var pdfCanvas = document.querySelector(selector);
        if (pdfCanvas) {
            pdfCanvas.scrollTop = 0;
        }
    }
</script>

@code {
    private byte[]? PdfSource { get; set; }

    private string PdfViewerClass { get; set; } = "scrollable-pdf-viewer";

    private async Task OnPdfViewerOpen()
    {
        await js.InvokeVoidAsync("scrollPdfToTop", $".{PdfViewerClass} .k-pdf-viewer-canvas");
    }
}

After clicking the Print button, the pages are ordered incorrectly. Can be seen in the preview window.

Steps to reproduce:

1. Open https://demos.telerik.com/blazor-ui/pdfviewer/overview

2. Click the Print button

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

Expected - the PDF must be downloaded.

Current - the file is not downloaded.

We're currently working on requiring a Google CASA Security Assessment, as part of this they scanned our site. 

However, the scan found an eval() function in the telerik-blazor.js file:

if(_util.isNodeJS){const worker=eval("require")(this.workerSrc);return worker.WorkerMessageHandler}

Is it possible to remove eval() from telerik-blazor.js?

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 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.

I would like to have access to the search option of the pdf viewer.
I have an old Asp.net framework site hosting the scanned pages (57.000) of the local newspaper from its start in May 1945 and want to rewrite it in Blazor.

One of the features is that you can search for words on all pages (using SQL Full-text indexing search on a table with all the plain texts to quickly locate the pages containing these words) and when a found page is clicked show the pdf of that page and prefill the searchbox of the pdf viewer to automatic highlight the found words).

This article gives a solution to achieve that in JS, but it would be nice if this could be done from de C# code https://www.telerik.com/forums/open-pdfviewer-with-highlighted-text

Kind regards,

Kees Alderliesten

Pdf viewer should display form fields like Text fields, check boxes, etc and allow users to type in fields.  Also support form field calculations.

Once populated, allow client side save to a file blob so that the data could be posted to a server or really whatever the dev wanted to do with it.

Adding the ability to fill in a PDF online in the PDF Viewer would open a lot of opportunity to the library.

The ability to fill-out, sign, and date would be great with a save callback, so it can be pushed to an API.

This request is for allowing to open other document types in PDF Viewer - for example, Word, Excel. The functionality will target viewing only and not editing.

1. Handle the OnOpen event to get the file bytes
2. Use the appropriate format provider of the RadSpreadProcessing library to import the Word/Excel file
3. Export the file with the PdfFormatProvider
4. Pass the converted file to the PDF Viewer to display it

Note: We've registered a bug with this solution. The PDF Viewer does not open other types of documents from the FileSelect in the Toolbar, they can be opened only on initialization of the component. Currently, the bug is in our backlog. Once fixed, the above-listed solution can be used to configure the PDF Viewer for viewing other document types. A knowledge base resource will be published on the matter.