Hi team,
I experience a Content Security Policy issue with the pdf viewer widget.
Dojo: https://dojo.telerik.com/qPYnmOBn
It seems to be dependent of the file though but not quite sure. Try this pdf file : https://www.arcep.fr/uploads/tx_gspublication/referentiel_general_ecoconception_des_services_numeriques_version_2024.pdf
and go to page 20 for instance.
Please advise.
Regards,
Laurent.
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 ]
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
PDFViewer focuses zoom input when the user clicks on zoom-in icon in Safari on iPhone and iPad
Reproduction of the problem
Dojo: https://dojo.telerik.com/AvOZeriz
Click on zoom in icon
Expected/desired behavior
Focus shall remain on the zoom in icon
Environment
Kendo UI version: [all]
Browser: [Safari]
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.
When the PDFViewer is created and a file is loaded using the fromFile method a new thread will be created. That thread remains in memory and doesn't get destroyed when the entire widget is destroyed.
$("#pdfViewer").data("kendoPDFViewer").destroy(); $("#pdfViewer").empty();
That created thread remains in memory and doesn't get destroyed.
The thread should get destroyed when the widget is destroyed.
###Workaround
A possible workaround:
kendoPDFViewer.processor.pdf.loadingTask.destroy();
The issue should be additionally researched as there are some leftovers in the JS Heap even when the workaround is used.
In PDFViewer, underlines increase size when zooming in/out.
The underlines increase their size.
The underlines should remain the same.