I have experience with OpenText Brava Enterprise. I've had the chance to integrate their Viewer in our in-house document management system. This viewer opens up to 100 file formats and allows to add/remove/edit annotations on files and saves these annotations as a separate layer on top of the file. So next time you open the same file to view, you can load the annotations (via API) calls and place the layer of annotations on top.
I was hoping I would see the same thing with Telerik PDF Viewer (and I am aware this works only for PDF). To allow the user to add a Text comment, Shapes, Stamps, Image, PDF Bookmark, etc.
Currently, when the PDFViewer is used with the latest pdf.js version 4.0.379 an error is thrown in the browser console. (Uncaught (in promise) Error: No "textContentSource" parameter specified.)
You can test the behavior in the Dojo linked here - https://dojo.telerik.com/@NeliKondova/eBUYEDAb. Run the example and wait for the pdf file to be loaded, then check the browser console.
The latest Kendo version is compatible with pdf.js version 3.11.174. However, I would like the Kendo UI for jQuery to be compatible with pdf.js 4.x to avoid such misbehaviors.
Hello,
I have an 8mb PDF files that I need to be able to search, however when I click on the search tool the entire page starts responding.
This issue happens in your hosted demo. It seems to come as a result of images in the PDF.
What do I need to do to have it work properly?
Thanks,
Greg
Dear Team,
As like in other frameworks (https://pspdfkit.com/) we should have the in built option to rotate the PDF pages using Kendo UI PDFViewer widget.
Regards,
Velusamy
Both Chrome and Firefox now have native PDF viewer support including the ability to display and navigate bookmarks within the document. Kendo’s control doesn’t have this functionality, but it’s possible to implement since PDF.js does and the Kendo control supports PDF.js rendering.
We’d really like to have a common UI for viewing documents within our web application, but we’re currently forced to render PDFs natively for Chrome and Firefox and with limited bookmark functionality for Internet Explorer by way of partial bookmark functionality we’ve implemented on top of the Kendo control.
Allow bookmarks to be set in the PDFViewer’s configuration during initialization, and then add a method to allow them to be scrolled-to by id. The bookmarks would simply be y-coordinate/page number pairs. It’d also be nice if the viewer could read the bookmarks directly, but not entirely necessary with PDF.js rendering since they can be read from PDF.js
Ideally, you could also expose the raw PDF.js document object used by the PDFViewer so that it could be used instead.
Hi,
Is a thumbnail/page viewer in discussion? It would be a real advantage to be able to see thumbs of pages alongside the page viewer.
An example using a different sdk is shown below.
URL:
http://atalasoft-viewer-demo.azurewebsites.net/
Regards,
Graham O'Riley
Netdocs
Bug report
PDF with a mixture of portrait and landscape pages shows incorrect page numbers in PDFViewer
Reproduction of the problem
Dojo: https://dojo.telerik.com/VtqGfXZA
Load a PDF with mixture of portrait and landscape pages.
Environment
jQuery: 3.4.1
Kendo UI version: 2024.3.1015
Browser: [all ]
Go to:
Demo of core features in jQuery PDFViewer widget | Kendo UI for jQuery (telerik.com). Note that pdf has 3 pages.
In the pdf viewer component demo select the printer icon and a print preview window opens. When the print preview window opens, note that the window indicates that there are 5 pages to print in the print preview. One page is added before the pdf pages and one after. This happens regardless of the printer selected.
Expected behavior: only 3 pages of the pdf should show in the print preview window.
The Actual Width option in the PDFViewer does not work as expected. The width rendered in the component does not match the actual width of the file.
Test scenario: a file that has 11.69 inches width ( approx. 1122 pixels ) is displayed with ~840px width.
The page width rendered from the Actual Width feature does not match the actual file width
The page width from the Actual Width option should match the actual page size of the file.
Unable to print PDFViewer's PDF on Safari
Regression since 2022.2.802 , most probably related to the following fix in that release - #6923
The Print Options window is loaded, but PDF pages are not shown in the Print preview. PDF pages content is not present in the saved PDF, if we save the printed content to file.
PDF pages are shown in the print preview window of Safari and can be saved to PDF
Working version 2022.2.621 - https://runner.telerik.io/fullscreen/abePoXEy
### Bug report
The PDFViewer requires the "unsafe-inline" keyword in the "style-src" directive.
### Reproduction of the problem
1. Enable CSP and set the "style-src" directive to "self":
<meta http-equiv="Content-Security-Policy" content="style-src 'self' https://kendo.cdn.telerik.com;"/>
2. Create a PDFViewer:
<div id="pdfviewer"></div>
<script src="https://cdnjs.cloudflare.com/ajax/libs/pdf.js/3.4.120/pdf.min.js"></script>
<script>
window.pdfjsLib.GlobalWorkerOptions.workerSrc = 'https://cdnjs.cloudflare.com/ajax/libs/pdf.js/3.4.120/pdf.worker.min.js';
</script>
<script>
$("#pdfviewer").kendoPDFViewer({
pdfjsProcessing: {
file: ""
}
});
</script>
A Dojo sample for reproduction: https://dojo.telerik.com/ugAyagIJ
### Current behavior
When the PDFViewer is initialized, the following Content Security Policy error is thrown:
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' https://kendo.cdn.telerik.com".
### Expected/desired behavior
The the 'unsafe-inline' keyword must not be required in the "style-src" directive when using the PDFViewer widget.
### Workaround:
Add the following script before the PDFViewer initialization:
<script>
var styles = {
scroller: "k-canvas k-pdf-viewer-canvas k-pos-relative k-overflow-auto"
};
kendo.ui.PDFViewer.fn._renderPageContainer = function () {
var that = this;
if (!that.pageContainer) {
that.pageContainerWrapper = $("<div />");
that.pageContainerWrapper.addClass(styles.scroller);
that.pageContainer = $(`<div class="k-pdf-viewer-pages" />`);
that.pageContainer.css('--scale-factor', that.zoomScale);
that.pageContainer.attr("tabindex", 0);
that.pageContainerWrapper.append(that.pageContainer);
that.wrapper.append(that.pageContainerWrapper);
}
};
</script>
### Environment
* **Kendo UI version: 2024.2.514
* **jQuery version: 3.7.0
* **Browser: [all]
Hi Team,
I understand at the moment there is a limitation to exporting Hierarchical Grids to PDF. I would like to request in the future a way to somehow overcome this.
Thank you!