Acro field values don't show in the PDF VIewer, although they display in the print preview dialog.

This is a regression in version 7.0.0. Version 6.2.0 displays the acro field values as expected.

===

TELERIK edit: This public item originally concerned to all Acro fields. We fixed the problem for editable Acro fields, while the fix for readonly ones can be tracked at PDF Viewer does not display readonly Acro fields

I want to have an option for digital signatures with browser-based certificate selection.

===

ADMIN EDIT

===

For the time being, you can use the following custom approach: Signing PDFs with PdfPRocessing in PdfViewer.

Hello,

we are using the PDFViewer Component. 

The zoom function usually works perfectly, both on mobile and desktop.

But there is one exception.

There is one scenario, where our PO got an crash, when he try to use ANY zoom functionality of the component. 

He is using:

• a Samsung Galaxy S21 FE 5G
• Android 14
• Chrome Browser

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

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?

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");
    }
}

We still have some problems with printed pdf quality after the updates in 6.0.0. When pdf is printed using Telerik PDF viewer it seems it gets processed/rasterized and loses quality.

Hello, I like the Telerik PDF Viewer for Blazor, but it's not supporting Table of Contents (TOC) links.  I would like to request this feature so that there are links in the TOC automatically.  I'm using Blazor WebAssembly.

Thank you for considering my request.

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

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.

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.