When a user invokes a Search tool, their intention is to directly write a text to search, therefore the edit for the search text should be focused immediately. In the current implementation, users have to manually focus the edit all the time, which is really inconvenient.

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

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.

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.