2013-07-13 03:14:13 +09:00
|
|
|
/* Copyright 2013 Mozilla Foundation
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*/
|
|
|
|
|
2021-02-24 21:02:58 +09:00
|
|
|
import { createObjectURL, createValidAbsoluteUrl, isPdfFile } from "pdfjs-lib";
|
2021-07-27 19:23:33 +09:00
|
|
|
import { compatibilityParams } from "./app_options.js";
|
2013-07-13 03:14:13 +09:00
|
|
|
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
if (typeof PDFJSDev !== "undefined" && !PDFJSDev.test("CHROME || GENERIC")) {
|
|
|
|
throw new Error(
|
|
|
|
'Module "pdfjs-web/download_manager" shall not be used ' +
|
|
|
|
"outside CHROME and GENERIC builds."
|
|
|
|
);
|
2017-02-28 20:41:43 +09:00
|
|
|
}
|
|
|
|
|
|
|
|
function download(blobUrl, filename) {
|
2019-12-27 08:22:32 +09:00
|
|
|
const a = document.createElement("a");
|
2018-02-12 18:27:56 +09:00
|
|
|
if (!a.click) {
|
|
|
|
throw new Error('DownloadManager: "a.click()" is not supported.');
|
2013-07-13 03:14:13 +09:00
|
|
|
}
|
2018-02-12 18:27:56 +09:00
|
|
|
a.href = blobUrl;
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
a.target = "_parent";
|
2018-02-12 18:27:56 +09:00
|
|
|
// Use a.download if available. This increases the likelihood that
|
|
|
|
// the file is downloaded instead of opened by another PDF plugin.
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
if ("download" in a) {
|
2018-02-12 18:27:56 +09:00
|
|
|
a.download = filename;
|
|
|
|
}
|
2020-09-06 00:00:52 +09:00
|
|
|
// <a> must be in the document for recent Firefox versions,
|
2018-02-12 18:27:56 +09:00
|
|
|
// otherwise .click() is ignored.
|
|
|
|
(document.body || document.documentElement).appendChild(a);
|
|
|
|
a.click();
|
|
|
|
a.remove();
|
2017-02-28 20:41:43 +09:00
|
|
|
}
|
2013-07-13 03:14:13 +09:00
|
|
|
|
2017-08-06 21:15:18 +09:00
|
|
|
class DownloadManager {
|
2021-02-23 20:58:17 +09:00
|
|
|
constructor() {
|
|
|
|
this._openBlobUrls = new WeakMap();
|
|
|
|
}
|
|
|
|
|
2017-08-06 21:15:18 +09:00
|
|
|
downloadUrl(url, filename) {
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
if (!createValidAbsoluteUrl(url, "http://example.com")) {
|
2017-02-28 20:41:43 +09:00
|
|
|
return; // restricted/invalid URL
|
|
|
|
}
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
download(url + "#pdfjs.action=download", filename);
|
2017-08-06 21:15:18 +09:00
|
|
|
}
|
2014-03-19 05:32:47 +09:00
|
|
|
|
2017-08-06 21:15:18 +09:00
|
|
|
downloadData(data, filename, contentType) {
|
2019-12-27 08:22:32 +09:00
|
|
|
const blobUrl = createObjectURL(
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
data,
|
|
|
|
contentType,
|
2021-07-27 19:23:33 +09:00
|
|
|
compatibilityParams.disableCreateObjectURL
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
);
|
2017-02-28 20:41:43 +09:00
|
|
|
download(blobUrl, filename);
|
2017-08-06 21:15:18 +09:00
|
|
|
}
|
2013-07-13 03:14:13 +09:00
|
|
|
|
2021-02-23 20:58:17 +09:00
|
|
|
/**
|
|
|
|
* @returns {boolean} Indicating if the data was opened.
|
|
|
|
*/
|
|
|
|
openOrDownloadData(element, data, filename) {
|
2021-02-24 21:02:58 +09:00
|
|
|
const isPdfData = isPdfFile(filename);
|
|
|
|
const contentType = isPdfData ? "application/pdf" : "";
|
2021-02-23 20:58:17 +09:00
|
|
|
|
2021-07-27 19:23:33 +09:00
|
|
|
if (isPdfData && !compatibilityParams.disableCreateObjectURL) {
|
2021-02-23 20:58:17 +09:00
|
|
|
let blobUrl = this._openBlobUrls.get(element);
|
|
|
|
if (!blobUrl) {
|
|
|
|
blobUrl = URL.createObjectURL(new Blob([data], { type: contentType }));
|
|
|
|
this._openBlobUrls.set(element, blobUrl);
|
|
|
|
}
|
|
|
|
let viewerUrl;
|
|
|
|
if (typeof PDFJSDev === "undefined" || PDFJSDev.test("GENERIC")) {
|
|
|
|
// The current URL is the viewer, let's use it and append the file.
|
|
|
|
viewerUrl = "?file=" + encodeURIComponent(blobUrl + "#" + filename);
|
|
|
|
} else if (PDFJSDev.test("CHROME")) {
|
|
|
|
// In the Chrome extension, the URL is rewritten using the history API
|
|
|
|
// in viewer.js, so an absolute URL must be generated.
|
|
|
|
viewerUrl =
|
|
|
|
// eslint-disable-next-line no-undef
|
|
|
|
chrome.runtime.getURL("/content/web/viewer.html") +
|
|
|
|
"?file=" +
|
|
|
|
encodeURIComponent(blobUrl + "#" + filename);
|
|
|
|
}
|
|
|
|
|
|
|
|
try {
|
|
|
|
window.open(viewerUrl);
|
|
|
|
return true;
|
|
|
|
} catch (ex) {
|
|
|
|
console.error(`openOrDownloadData: ${ex}`);
|
|
|
|
// Release the `blobUrl`, since opening it failed, and fallback to
|
|
|
|
// downloading the PDF file.
|
|
|
|
URL.revokeObjectURL(blobUrl);
|
|
|
|
this._openBlobUrls.delete(element);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
this.downloadData(data, filename, contentType);
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2020-08-20 04:19:59 +09:00
|
|
|
/**
|
|
|
|
* @param sourceEventType {string} Used to signal what triggered the download.
|
|
|
|
* The version of PDF.js integrated with Firefox uses this to to determine
|
|
|
|
* which dialog to show. "save" triggers "save as" and "download" triggers
|
|
|
|
* the "open with" dialog.
|
|
|
|
*/
|
|
|
|
download(blob, url, filename, sourceEventType = "download") {
|
2021-07-27 19:23:33 +09:00
|
|
|
if (compatibilityParams.disableCreateObjectURL) {
|
2017-02-28 20:41:43 +09:00
|
|
|
// URL.createObjectURL is not supported
|
|
|
|
this.downloadUrl(url, filename);
|
|
|
|
return;
|
2013-07-13 03:14:13 +09:00
|
|
|
}
|
2019-12-27 08:22:32 +09:00
|
|
|
const blobUrl = URL.createObjectURL(blob);
|
2017-02-28 20:41:43 +09:00
|
|
|
download(blobUrl, filename);
|
2017-08-06 21:15:18 +09:00
|
|
|
}
|
|
|
|
}
|
2017-02-28 20:41:43 +09:00
|
|
|
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
export { DownloadManager };
|