-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[api-minor] Update the minimum supported browser versions #14538
Conversation
Please note that while we "support" some (by now) fairly old browsers, that essentially means that the library (and viewer) will load and that the basic functionality will work as intended.[1] However, in older browsers, some functionality may not be available and generally we'll ask users to update to a modern browser when bugs (specific to old browsers) are reported.[2] There's always a question of just how old browsers the PDF.js contributors can realistically support, and here I'm suggesting that we place the cut-off point at approximately *three* years. With that in mind, this patch updates the *minimum* supported browsers (and environments) as follows: - Chrome 73, which was released on 2019-03-12; see https://en.wikipedia.org/wiki/Google_Chrome_version_history - Firefox ESR (as before); see https://wiki.mozilla.org/Release_Management/Calendar - Safari 12.1, which was released on 2019-03-25; see https://en.wikipedia.org/wiki/Safari_version_history#Safari_12 - Node.js 12, which was release on 2019-04-23 (and will soon reach EOL); see https://en.wikipedia.org/wiki/Node.js#Releases --- [1] Assuming a `legacy`-build is being used, of course. [2] In general it's never a good idea to use an old/outdated browser, since those may contain *known* security vulnerabilities.
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/e8b567e455326f2/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/e8b567e455326f2/output.txt Total script time: 4.36 mins Published |
/botio test |
From: Bot.io (Linux m4)ReceivedCommand cmd_test from @timvandermeij received. Current queue size: 0 Live output at: http://54.241.84.105:8877/77c15604a52385e/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_test from @timvandermeij received. Current queue size: 1 Live output at: http://54.193.163.58:8877/4905f693bf2bda2/output.txt |
From: Bot.io (Linux m4)FailedFull output at http://54.241.84.105:8877/77c15604a52385e/output.txt Total script time: 23.54 mins
Image differences available at: http://54.241.84.105:8877/77c15604a52385e/reftest-analyzer.html#web=eq.log |
From: Bot.io (Windows)SuccessFull output at http://54.193.163.58:8877/4905f693bf2bda2/output.txt Total script time: 24.64 mins
|
I fully agree with this; three years seems like a very reasonable cutoff point to me too. |
Please note that while we "support" some (by now) fairly old browsers, that essentially means that the library (and viewer) will load and that the basic functionality will work as intended.[1]
However, in older browsers, some functionality may not be available and generally we'll ask users to update to a modern browser when bugs (specific to old browsers) are reported.[2]
There's always a question of just how old browsers the PDF.js contributors can realistically support, and here I'm suggesting that we place the cut-off point at approximately three years.
With that in mind, this patch updates the minimum supported browsers (and environments) as follows:
[1] Assuming a
legacy
-build is being used, of course.[2] In general it's never a good idea to use an old/outdated browser, since those may contain known security vulnerabilities.