mozilla/pdf.js

Remove the `pageRotation` getter in `PDFViewerApplication`

This was added, during the refactoring in PR 8556, to avoid outright breaking third-party users of the default viewer.
With PDF.js version `2.0`, where we're making API changes that aren't backwards compatible, we ought to be able to remove this piece of viewer code as well.

…ignature

Remove the unused `capability` parameter from the `WorkerTransport.getPage` method

…tPage` method

That parameter, originally named `promise`, has been unused for over five years; ever since commit f0687c4 in PR 1531.

Split the existing `WebGLUtils` in two classes, a private `WebGLUtils` and a public `WebGLContext`, and utilize the latter in the API to allow various code to access the methods of `WebGLUtils`

…` and a public `WebGLContext`, and utilize the latter in the API to allow various code to access the methods of `WebGLUtils`

This patch is one (small) step on the way to reduce the general dependency on a global `PDFJS` object, for PDF.js version `2.0`.

Update eslint-plugin-mozilla, and enable mozilla/use-services rule.

…errors

Don't display error messages, in the default viewer, for PDF files other than the current one

…her than the current one

We've never attempted to limit the errors displayed in the default viewer to the current PDF file, but that's not really been a problem before. However after PR 7926, it's now possible to get password related error messages for *previously* opened PDF files in the default viewer.

**STR:**
 1. Open a password protected PDF file, e.g. `issue6010_1.pdf` from the test-suite.
 2. Cancel the password prompt.
 3. Open any new PDF file in the viewer.

**AR:**
The error UI is displayed, with a `No password given` message.

**ER:**
No error displayed, since it's only relevent for a now closed PDF file.

This is obviously a minor issue, caused by us now rejecting the still pending `pdfLoadingTask` during the `PDFViewerApplication.close` call, but I don't think that it (generally) makes sense to show errors if they're not relevant to the *currently* displayed PDF file.

Remove more polyfills for old browsers

Add mgol's name to AUTHORS, add .mailmap

In this way mgol's past contribution is mapped correctly.

This was only relevant for no obsolete versions Opera, that use the Presto engine. According to https://en.wikipedia.org/wiki/History_of_the_Opera_web_browser#Opera_2013, the last version affected was released in 2013.

This is only relevant for browsers that we don't intend to support with PDF.js version `2.0`.

This is only relevant for browsers that we don't intend to support with PDF.js version `2.0`.

This is only relevant for browsers that we don't intend to support with PDF.js version `2.0`.

This is only relevant for browsers that we don't intend to support with PDF.js version `2.0`.

Update index.md

adding commas each in two sentences in order to make readers fully understand when reading index.md and to organize the context properly based on grammatical rules.

Sanitize the display value for choice widget annotations

Remove the `console` polyfills

Update index.md

Re-factor how parameters are passed to the network streams

fixing grammatical error (demonstrate -> demonstrates)

Update README.md

Clarifying what IRC stands for in order to make people understand clearly who want to use relay chat in irc.mozilla.org

Fix the interface of `JpegStream`/`JpxStream`/`Jbig2Stream` to agree with the other `DecodeStream`s

…rom-examples

Remove mentions of compatibility.js from examples

…r-parsing

Extract parsing of debugging hash parameters into its own method in `PDFViewerApplication`

Filling and stroking empty paths in SVG backend