From c9d687bee463a26d87acb982795987cd1cc6be73 Mon Sep 17 00:00:00 2001 From: Jonas Jenwald Date: Fri, 23 Sep 2022 10:59:31 +0200 Subject: [PATCH] Try to improve the supported browsers documentation --- Frequently-Asked-Questions.md | 44 ++++++++++++++++++++++++----------- 1 file changed, 31 insertions(+), 13 deletions(-) diff --git a/Frequently-Asked-Questions.md b/Frequently-Asked-Questions.md index 33f5e81..a70706b 100644 --- a/Frequently-Asked-Questions.md +++ b/Frequently-Asked-Questions.md @@ -32,25 +32,43 @@ You can use raw binary data to open a PDF document: use Uint8Array instead of UR Not by default, but it is possible. PDF.js runs with the same permissions as any other JavaScript code, which means it cannot do cross origin requests (see [Same origin policy](http://en.wikipedia.org/wiki/Same_origin_policy) and [an example](https://gist.github.com/3452072)). There are some possible ways to get around this such as using [CORS](http://enable-cors.org/) (see also [unsafe headers issue](https://github.com/mozilla/pdf.js/issues/3150#issuecomment-17582371) and [Access-Control-Expose-Headers issue](https://github.com/mozilla/pdf.js/issues/4530)) or setting up a proxy on your server that will feed PDF.js the PDF file (example: https://github.com/mozilla/pdf.js/issues/1000#issuecomment-133756244). Please notice that generic/demo viewer blocks this functionality if deployed not on mozilla.github.io domain to avoid content spoofing (see https://github.com/mozilla/pdf.js/pull/6916). -## Which browsers are supported? -From version `2.4.456` on we produce a non-translated/non-polyfilled build for modern browsers by default. However, we also provide the translated/polyfilled build for older browsers in a separate bundle (with the `-legacy-dist.zip` suffix). +## Which browsers/environments are supported? +By default we produce a non-translated/non-polyfilled build, intended for *the latest* browsers. However, we also provide a translated/polyfilled build for older browsers in a separate bundle (with a `legacy` suffix). -The objective is to support all HTML5 compliant browsers, but since feature support varies per browser/version our support for all PDF features varies as well. In general, the support is below. If no version is indicated, then the latest desktop/mobile versions are intended. +The objective is to support all HTML5 compliant browsers, but since feature support varies per browser/version our support for all PDF features varies as well. In general, the support is listed below. If no version is indicated, then *the latest* desktop/mobile versions are implied. +### Modern build - + - + - + +
BrowserSupportedAutomated testingNotes
Browser/environmentSupportedAutomated testingNotes
Firefox ESR+Firefox Yes Windows/Linux
Chrome 76+Chrome Yes Windows/Linux
+ +### `legacy` build + + + + + + + + + + + + + + @@ -58,22 +76,22 @@ The objective is to support all HTML5 compliant browsers, but since feature supp - + - + - + - - - - + + + +
Browser/environmentSupportedAutomated testingNotes
Firefox ESR+YesNone
Chrome 85+YesNone
Opera Yes
Edge (Chromium-based)Edge Yes NoneOnly the Chromium-based version is supported.
Safari 13.1+Safari 14+ Mostly None Some missing features/defects have been reported, but no problems in general.
IE/Edge (not Chromium-based)NoNoneToo many missing features to be supported.Node.js 14+MostlyLimitedSome missing features, but no problems in general.