pdf.js

History

Jonas Jenwald a9ce4e8417 Stop exposing the `URL` polyfill in the global scope This moves/exposes the `URL` polyfill similarily to the existing `ReadableStream` polyfill, rather than exposing it globally, to avoid interfering with any "outside" code. Both the `URL` and `ReadableStream` polyfills are now exposed on the `pdfjsLib` object, such that they are accessible to the viewer components. Furthermore, the `no-restricted-globals` ESLint rule is also enabled to prevent accidental usage of the native `URL`/`ReadableStream` implementations directly in the `src/` and `web/` folders; see also https://eslint.org/docs/rules/no-restricted-globals Addresses the remaining TODO in https://github.com/mozilla/pdf.js/projects/6	2018-07-04 09:16:28 +02:00
..
url-lib.js	Stop exposing the `URL` polyfill in the global scope	2018-07-04 09:16:28 +02:00

Jonas Jenwald a9ce4e8417 Stop exposing the URL polyfill in the global scope

This moves/exposes the `URL` polyfill similarily to the existing `ReadableStream` polyfill, rather than exposing it globally, to avoid interfering with any "outside" code.
Both the `URL` and `ReadableStream` polyfills are now exposed on the `pdfjsLib` object, such that they are accessible to the viewer components.
Furthermore, the `no-restricted-globals` ESLint rule is also enabled to prevent accidental usage of the native `URL`/`ReadableStream` implementations directly in the `src/` and `web/` folders; see also https://eslint.org/docs/rules/no-restricted-globals

Addresses the remaining TODO in https://github.com/mozilla/pdf.js/projects/6

2018-07-04 09:16:28 +02:00

url-lib.js Stop exposing the URL polyfill in the global scope 2018-07-04 09:16:28 +02:00