From 57b0a163fedb4b5a9889b98156f3af4e90177093 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Calvi=C3=B1o=20S=C3=A1nchez?= Date: Fri, 28 Apr 2023 03:36:12 +0200 Subject: [PATCH] Remove outdated comment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Since PDF.js was bumped to 2.5.207 in 4705de45c4 the event listened to is "DOMContentLoaded" rather than "webviewerloaded". Signed-off-by: Daniel Calviño Sánchez --- src/workersrc.js | 7 ------- 1 file changed, 7 deletions(-) diff --git a/src/workersrc.js b/src/workersrc.js index cdb97d60..dd036d4b 100644 --- a/src/workersrc.js +++ b/src/workersrc.js @@ -34,13 +34,6 @@ const queryString = window.location.search const urlParams = new URLSearchParams(queryString) const canDownload = urlParams.get('canDownload') -// When "PDFViewerApplication.webViewerInitialized" is executed (once -// "PDFViewerApplication.initialize" is done) it opens the PDF file via URL, -// which requires the PDFViewerApplication to be properly configured, so the -// custom initialization has to be executed before that. This can be done by -// listening to the "webviewerloaded" event, which is emitted after -// "PDFViewerApplication" and "PDFViewerApplicationOptions" are globally set and -// before "PDFViewerApplication.initialize" is executed. function initializeCustomPDFViewerApplication() { const head = document.getElementsByTagName('head')[0]