From 9887644702aa8ec4fa8faeeedbee0aa673cf7799 Mon Sep 17 00:00:00 2001 From: Jonas Jenwald Date: Tue, 16 Feb 2021 16:23:53 +0100 Subject: [PATCH] Stop showing the fallback bar for "errorFontMissing" errors (PR 11218 follow-up) *This is somewhat similar to PR 12931.* For PDF documents where fonts are completely missing in the /Resources dictionaries, there's basically no "correct" way of rendering the document. Hence it's very unlikely that another PDF viewer will do a better job than PDF.js in these cases, and consequently it seems highly questionable if the fallback bar really helps here. --- web/app.js | 1 + 1 file changed, 1 insertion(+) diff --git a/web/app.js b/web/app.js index 5f4cc827c..eb3c0abc6 100644 --- a/web/app.js +++ b/web/app.js @@ -1082,6 +1082,7 @@ const PDFViewerApplication = { // user-visible errors, to avoid bothering the user unnecessarily. switch (featureId) { case UNSUPPORTED_FEATURES.errorFontLoadNative: + case UNSUPPORTED_FEATURES.errorFontMissing: return; } // Only trigger the fallback once so we don't spam the user with messages