[Tracking] Back-port patches to the current PDF.js pre-release (v2.4.456)

One of the most significant changes in the current PDF.js pre-release, see https://github.com/mozilla/pdf.js/releases/tag/v2.4.456, is that we’re now producing two kind of builds (with/without Babel translation and polyfills).

This has lead to some issues and/or support questions, since the default PDF.js builds are no longer directly compatible with “all” browsers/environments. Hence we may want to consider back-porting only the following patches (the list below is subject to change), using git cherry-pick, to the v2.4.456 pre-release and then replace it with a new version.

• https://github.com/mozilla/pdf.js/pull/11771
• https://github.com/mozilla/pdf.js/pull/11799
• https://github.com/mozilla/pdf.js/pull/11837

---

Given that the release was done less than a month ago, as of this writing, we probably want to wait a bit before making a final decision (there may be additional issues/regressions that should be addressed).

While I don’t have any data and/or statistics to back up this claim, but based on experience it seems that many (most?) users will only ever use “stable” releases. Hence fixing these issues at the pre-release stage seem much simpler, rather than having them reach an actual release version (which is why I opened this tracking issue).

[timvandermeij]

Good plan. I’ll try to do this soon since there is a demand for the new version.

[timvandermeij]

Let’s indeed see if more people run into problems with this before making a final decision.