2016-05-29 23:44:50 +09:00
|
|
|
/*
|
|
|
|
Copyright 2016 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.
|
|
|
|
*/
|
Switch to using ESLint, instead of JSHint, for linting
*Please note that most of the necessary code adjustments were made in PR 7890.*
ESLint has a number of advantageous properties, compared to JSHint. Among those are:
- The ability to find subtle bugs, thanks to more rules (e.g. PR 7881).
- Much more customizable in general, and many rules allow fine-tuned behaviour rather than the just the on/off rules in JSHint.
- Many more rules that can help developers avoid bugs, and a lot of rules that can be used to enforce a consistent coding style. The latter should be particularily useful for new contributors (and reduce the amount of stylistic review comments necessary).
- The ability to easily specify exactly what rules to use/not to use, as opposed to JSHint which has a default set. *Note:* in future JSHint version some of the rules we depend on will be removed, according to warnings in http://jshint.com/docs/options/, so we wouldn't be able to update without losing lint coverage.
- More easily disable one, or more, rules temporarily. In JSHint this requires using a numeric code, which isn't very user friendly, whereas in ESLint the rule name is simply used instead.
By default there's no rules enabled in ESLint, but there are some default rule sets available. However, to prevent linting failures if we update ESLint in the future, it seemed easier to just explicitly specify what rules we want.
Obviously this makes the ESLint config file somewhat bigger than the old JSHint config file, but given how rarely that one has been updated over the years I don't think that matters too much.
I've tried, to the best of my ability, to ensure that we enable the same rules for ESLint that we had for JSHint. Furthermore, I've also enabled a number of rules that seemed to make sense, both to catch possible errors *and* various style guide violations.
Despite the ESLint README claiming that it's slower that JSHint, https://github.com/eslint/eslint#how-does-eslint-performance-compare-to-jshint, locally this patch actually reduces the runtime for `gulp` lint (by approximately 20-25%).
A couple of stylistic rules that would have been nice to enable, but where our code currently differs to much to make it feasible:
- `comma-dangle`, controls trailing commas in Objects and Arrays (among others).
- `object-curly-spacing`, controls spacing inside of Objects.
- `spaced-comment`, used to enforce spaces after `//` and `/*. (This is made difficult by the fact that there's still some usage of the old preprocessor left.)
Rules that I indend to look into possibly enabling in follow-ups, if it seems to make sense: `no-else-return`, `no-lonely-if`, `brace-style` with the `allowSingleLine` parameter removed.
Useful links:
- http://eslint.org/docs/user-guide/configuring
- http://eslint.org/docs/rules/
2016-12-15 23:52:29 +09:00
|
|
|
/* eslint strict: ["error", "function"] */
|
2016-05-29 23:44:50 +09:00
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
(function () {
|
2016-05-29 23:44:50 +09:00
|
|
|
"use strict";
|
|
|
|
// This module sends the browser and extension version to a server, to
|
|
|
|
// determine whether it is safe to drop support for old Chrome versions in
|
|
|
|
// future extension updates.
|
|
|
|
//
|
|
|
|
// The source code for the server is available at:
|
|
|
|
// https://github.com/Rob--W/pdfjs-telemetry
|
|
|
|
var LOG_URL = "https://pdfjs.robwu.nl/logpdfjs";
|
|
|
|
|
|
|
|
// The minimum time to wait before sending a ping, so that we don't send too
|
|
|
|
// many requests even if the user restarts their browser very often.
|
|
|
|
// We want one ping a day, so a minimum delay of 12 hours should be OK.
|
|
|
|
var MINIMUM_TIME_BETWEEN_PING = 12 * 36e5;
|
|
|
|
|
|
|
|
if (chrome.extension.inIncognitoContext) {
|
|
|
|
// The extension uses incognito split mode, so there are two background
|
|
|
|
// pages. Only send telemetry when not in incognito mode.
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (chrome.runtime.id !== "oemmndcbldboiebfnladdacbdfmadadm") {
|
|
|
|
// Only send telemetry for the official PDF.js extension.
|
|
|
|
console.warn("Disabled telemetry because this is not an official build.");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
maybeSendPing();
|
|
|
|
setInterval(maybeSendPing, 36e5);
|
|
|
|
|
|
|
|
function maybeSendPing() {
|
2020-04-14 19:28:14 +09:00
|
|
|
getLoggingPref(function (didOptOut) {
|
2016-05-29 23:44:50 +09:00
|
|
|
if (didOptOut) {
|
|
|
|
// Respect the user's decision to not send statistics.
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (!navigator.onLine) {
|
|
|
|
// No network available; Wait until the next scheduled ping opportunity.
|
|
|
|
// Even if onLine is true, the server may still be unreachable. But
|
|
|
|
// because it is impossible to tell whether a request failed due to the
|
|
|
|
// inability to connect, or a deliberate connection termination by the
|
|
|
|
// server, we don't validate the response and assume that the request
|
|
|
|
// succeeded. This ensures that the server cannot ask the client to
|
|
|
|
// send more pings.
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
var lastTime = parseInt(localStorage.telemetryLastTime) || 0;
|
|
|
|
var wasUpdated = didUpdateSinceLastCheck();
|
|
|
|
if (!wasUpdated && Date.now() - lastTime < MINIMUM_TIME_BETWEEN_PING) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
localStorage.telemetryLastTime = Date.now();
|
|
|
|
|
|
|
|
var deduplication_id = getDeduplicationId(wasUpdated);
|
|
|
|
var extension_version = chrome.runtime.getManifest().version;
|
2023-07-03 00:10:17 +09:00
|
|
|
fetch(LOG_URL, {
|
|
|
|
method: "POST",
|
|
|
|
headers: new Headers({
|
|
|
|
"Deduplication-Id": deduplication_id,
|
|
|
|
"Extension-Version": extension_version,
|
|
|
|
}),
|
|
|
|
// Set mode=cors so that the above custom headers are included in the
|
|
|
|
// request.
|
|
|
|
mode: "cors",
|
|
|
|
// Omits credentials such as cookies in the requests, which guarantees
|
|
|
|
// that the server cannot track the client via HTTP cookies.
|
|
|
|
credentials: "omit",
|
|
|
|
cache: "no-store",
|
|
|
|
});
|
2016-05-29 23:44:50 +09:00
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Generate a 40-bit hexadecimal string (=10 letters, 1.1E12 possibilities).
|
|
|
|
* This is used by the server to discard duplicate entries of the same browser
|
|
|
|
* version when the log data is aggregated.
|
|
|
|
*/
|
|
|
|
function getDeduplicationId(wasUpdated) {
|
|
|
|
var id = localStorage.telemetryDeduplicationId;
|
|
|
|
// The ID is only used to deduplicate reports for the same browser version,
|
|
|
|
// so it is OK to change the ID if the browser is updated. By changing the
|
|
|
|
// ID, the server cannot track users for a long period even if it wants to.
|
|
|
|
if (!id || !/^[0-9a-f]{10}$/.test(id) || wasUpdated) {
|
|
|
|
id = "";
|
|
|
|
var buf = new Uint8Array(5);
|
|
|
|
crypto.getRandomValues(buf);
|
2022-07-17 22:48:39 +09:00
|
|
|
for (const c of buf) {
|
2016-05-29 23:44:50 +09:00
|
|
|
id += (c >>> 4).toString(16) + (c & 0xf).toString(16);
|
|
|
|
}
|
|
|
|
localStorage.telemetryDeduplicationId = id;
|
|
|
|
}
|
|
|
|
return id;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Returns whether the browser has received a major update since the last call
|
|
|
|
* to this function.
|
|
|
|
*/
|
|
|
|
function didUpdateSinceLastCheck() {
|
|
|
|
var chromeVersion = /Chrome\/(\d+)\./.exec(navigator.userAgent);
|
|
|
|
chromeVersion = chromeVersion && chromeVersion[1];
|
|
|
|
if (!chromeVersion || localStorage.telemetryLastVersion === chromeVersion) {
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
localStorage.telemetryLastVersion = chromeVersion;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Get the value of the telemetry preference. The callback is invoked with a
|
|
|
|
* boolean if a preference is found, and with the undefined value otherwise.
|
|
|
|
*/
|
|
|
|
function getLoggingPref(callback) {
|
|
|
|
// Try to look up the preference in the storage, in the following order:
|
|
|
|
var areas = ["sync", "local", "managed"];
|
|
|
|
|
|
|
|
next();
|
|
|
|
function next(result) {
|
|
|
|
var storageAreaName = areas.shift();
|
|
|
|
if (typeof result === "boolean" || !storageAreaName) {
|
|
|
|
callback(result);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!chrome.storage[storageAreaName]) {
|
|
|
|
next();
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
chrome.storage[storageAreaName].get("disableTelemetry", function (items) {
|
2016-05-29 23:44:50 +09:00
|
|
|
next(items && items.disableTelemetry);
|
|
|
|
});
|
|
|
|
}
|
|
|
|
}
|
|
|
|
})();
|