2016-05-23 15:50:07 +02: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.
|
|
|
|
*/
|
2024-09-02 01:34:25 +02:00
|
|
|
"use strict";
|
2016-05-23 15:50:07 +02:00
|
|
|
|
2024-09-02 01:34:25 +02:00
|
|
|
chrome.runtime.onInstalled.addListener(({ reason }) => {
|
|
|
|
if (reason !== "update") {
|
|
|
|
// We only need to run migration logic for extension updates, not for new
|
|
|
|
// installs or browser updates.
|
|
|
|
return;
|
|
|
|
}
|
2016-05-23 15:50:07 +02:00
|
|
|
var storageLocal = chrome.storage.local;
|
|
|
|
var storageSync = chrome.storage.sync;
|
|
|
|
|
|
|
|
if (!storageSync) {
|
|
|
|
// No sync storage area - nothing to migrate to.
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2020-04-14 12:28:14 +02:00
|
|
|
getStorageNames(function (storageKeys) {
|
|
|
|
storageLocal.get(storageKeys, function (values) {
|
2016-05-23 15:50:07 +02:00
|
|
|
if (!values || !Object.keys(values).length) {
|
|
|
|
// No local storage - nothing to migrate.
|
2017-07-15 01:50:15 +02:00
|
|
|
// ... except possibly for a renamed preference name.
|
|
|
|
migrateRenamedStorage();
|
2016-05-23 15:50:07 +02:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
migrateToSyncStorage(values);
|
|
|
|
});
|
|
|
|
});
|
|
|
|
|
2024-09-02 01:34:25 +02:00
|
|
|
async function getStorageNames(callback) {
|
2016-05-23 15:50:07 +02:00
|
|
|
var schema_location = chrome.runtime.getManifest().storage.managed_schema;
|
2024-09-02 01:34:25 +02:00
|
|
|
var res = await fetch(chrome.runtime.getURL(schema_location));
|
|
|
|
var storageManifest = await res.json();
|
|
|
|
var storageKeys = Object.keys(storageManifest.properties);
|
|
|
|
callback(storageKeys);
|
2016-05-23 15:50:07 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
// Save |values| to storage.sync and delete the values with that key from
|
|
|
|
// storage.local.
|
|
|
|
function migrateToSyncStorage(values) {
|
2020-04-14 12:28:14 +02:00
|
|
|
storageSync.set(values, function () {
|
2016-05-23 15:50:07 +02:00
|
|
|
if (chrome.runtime.lastError) {
|
|
|
|
console.error(
|
|
|
|
"Failed to migrate settings due to an error: " +
|
|
|
|
chrome.runtime.lastError.message
|
|
|
|
);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
// Migration successful. Delete local settings.
|
2020-04-14 12:28:14 +02:00
|
|
|
storageLocal.remove(Object.keys(values), function () {
|
2016-05-23 15:50:07 +02:00
|
|
|
// In theory remove() could fail (e.g. if the browser's storage
|
|
|
|
// backend is corrupt), but since storageSync.set succeeded, consider
|
|
|
|
// the migration successful.
|
|
|
|
console.log(
|
|
|
|
"Successfully migrated preferences from local to sync storage."
|
|
|
|
);
|
2017-07-15 01:50:15 +02:00
|
|
|
migrateRenamedStorage();
|
2016-05-23 15:50:07 +02:00
|
|
|
});
|
|
|
|
});
|
|
|
|
}
|
2017-07-15 01:50:15 +02:00
|
|
|
|
|
|
|
// TODO: Remove this migration code somewhere in the future, when most users
|
|
|
|
// have had their chance of migrating to the new preference format.
|
|
|
|
// Note: We cannot modify managed preferences, so the migration logic is
|
|
|
|
// duplicated in web/chromecom.js too.
|
|
|
|
function migrateRenamedStorage() {
|
|
|
|
storageSync.get(
|
|
|
|
[
|
|
|
|
"enableHandToolOnLoad",
|
|
|
|
"cursorToolOnLoad",
|
[CRX] Make textLayerMode pref visible and add migration logic
In a1cfa5f4d7c8fcf55e9f3b51a23885dca8782915, the textLayerMode
preference was introduced, to replace the disableTextLayer and
enhanceTextSelection preferences.
As a result, the text selection preference was no longer visible
in Chrome (because preferences are only rendered by default for
boolean preferences, not for enumerations).
This commit adds the necessary bits to
extensions/chromium/options/options.{html,js}
so that the textLayerMode preference can be changed again.
Also, migration logic has been added to move over preferences
from the old to the new names:
- In web/chromecom.js, the logic is added to translate
preferences that were set by an administrator (it is read-only,
so this layer is unavoidable).
- In extensions/chromium/options/migration.js, similar logic is
added, except in this case the preference storage is writable,
so this migration logic happens only once.
The "enhanced text selection" mode is still experimental, so it
has been marked as experimental to signal that there may be bugs.
The list of tasks that block promotion to stable is at #7584.
2018-02-16 18:02:05 +01:00
|
|
|
"disableTextLayer",
|
|
|
|
"enhanceTextSelection",
|
|
|
|
"textLayerMode",
|
2019-02-02 10:08:45 +01:00
|
|
|
"showPreviousViewOnLoad",
|
|
|
|
"disablePageMode",
|
|
|
|
"viewOnLoad",
|
2017-07-15 01:50:15 +02:00
|
|
|
],
|
2020-04-14 12:28:14 +02:00
|
|
|
function (items) {
|
2017-07-15 01:50:15 +02:00
|
|
|
// Migration code for https://github.com/mozilla/pdf.js/pull/7635.
|
|
|
|
if (typeof items.enableHandToolOnLoad === "boolean") {
|
|
|
|
if (items.enableHandToolOnLoad) {
|
|
|
|
storageSync.set(
|
|
|
|
{
|
|
|
|
cursorToolOnLoad: 1,
|
|
|
|
},
|
2020-04-14 12:28:14 +02:00
|
|
|
function () {
|
2017-07-15 01:50:15 +02:00
|
|
|
if (!chrome.runtime.lastError) {
|
|
|
|
storageSync.remove("enableHandToolOnLoad");
|
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 15:59:37 +01:00
|
|
|
}
|
2017-07-15 01:50:15 +02:00
|
|
|
}
|
|
|
|
);
|
|
|
|
} else {
|
|
|
|
storageSync.remove("enableHandToolOnLoad");
|
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 15:59:37 +01:00
|
|
|
}
|
2017-07-15 01:50:15 +02:00
|
|
|
}
|
[CRX] Make textLayerMode pref visible and add migration logic
In a1cfa5f4d7c8fcf55e9f3b51a23885dca8782915, the textLayerMode
preference was introduced, to replace the disableTextLayer and
enhanceTextSelection preferences.
As a result, the text selection preference was no longer visible
in Chrome (because preferences are only rendered by default for
boolean preferences, not for enumerations).
This commit adds the necessary bits to
extensions/chromium/options/options.{html,js}
so that the textLayerMode preference can be changed again.
Also, migration logic has been added to move over preferences
from the old to the new names:
- In web/chromecom.js, the logic is added to translate
preferences that were set by an administrator (it is read-only,
so this layer is unavoidable).
- In extensions/chromium/options/migration.js, similar logic is
added, except in this case the preference storage is writable,
so this migration logic happens only once.
The "enhanced text selection" mode is still experimental, so it
has been marked as experimental to signal that there may be bugs.
The list of tasks that block promotion to stable is at #7584.
2018-02-16 18:02:05 +01:00
|
|
|
// Migration code for https://github.com/mozilla/pdf.js/pull/9479.
|
|
|
|
if (typeof items.disableTextLayer === "boolean") {
|
2020-01-12 19:47:13 +01:00
|
|
|
if (items.disableTextLayer) {
|
[CRX] Make textLayerMode pref visible and add migration logic
In a1cfa5f4d7c8fcf55e9f3b51a23885dca8782915, the textLayerMode
preference was introduced, to replace the disableTextLayer and
enhanceTextSelection preferences.
As a result, the text selection preference was no longer visible
in Chrome (because preferences are only rendered by default for
boolean preferences, not for enumerations).
This commit adds the necessary bits to
extensions/chromium/options/options.{html,js}
so that the textLayerMode preference can be changed again.
Also, migration logic has been added to move over preferences
from the old to the new names:
- In web/chromecom.js, the logic is added to translate
preferences that were set by an administrator (it is read-only,
so this layer is unavoidable).
- In extensions/chromium/options/migration.js, similar logic is
added, except in this case the preference storage is writable,
so this migration logic happens only once.
The "enhanced text selection" mode is still experimental, so it
has been marked as experimental to signal that there may be bugs.
The list of tasks that block promotion to stable is at #7584.
2018-02-16 18:02:05 +01:00
|
|
|
storageSync.set(
|
|
|
|
{
|
2022-01-18 18:09:12 +01:00
|
|
|
textLayerMode: 0,
|
[CRX] Make textLayerMode pref visible and add migration logic
In a1cfa5f4d7c8fcf55e9f3b51a23885dca8782915, the textLayerMode
preference was introduced, to replace the disableTextLayer and
enhanceTextSelection preferences.
As a result, the text selection preference was no longer visible
in Chrome (because preferences are only rendered by default for
boolean preferences, not for enumerations).
This commit adds the necessary bits to
extensions/chromium/options/options.{html,js}
so that the textLayerMode preference can be changed again.
Also, migration logic has been added to move over preferences
from the old to the new names:
- In web/chromecom.js, the logic is added to translate
preferences that were set by an administrator (it is read-only,
so this layer is unavoidable).
- In extensions/chromium/options/migration.js, similar logic is
added, except in this case the preference storage is writable,
so this migration logic happens only once.
The "enhanced text selection" mode is still experimental, so it
has been marked as experimental to signal that there may be bugs.
The list of tasks that block promotion to stable is at #7584.
2018-02-16 18:02:05 +01:00
|
|
|
},
|
2020-04-14 12:28:14 +02:00
|
|
|
function () {
|
[CRX] Make textLayerMode pref visible and add migration logic
In a1cfa5f4d7c8fcf55e9f3b51a23885dca8782915, the textLayerMode
preference was introduced, to replace the disableTextLayer and
enhanceTextSelection preferences.
As a result, the text selection preference was no longer visible
in Chrome (because preferences are only rendered by default for
boolean preferences, not for enumerations).
This commit adds the necessary bits to
extensions/chromium/options/options.{html,js}
so that the textLayerMode preference can be changed again.
Also, migration logic has been added to move over preferences
from the old to the new names:
- In web/chromecom.js, the logic is added to translate
preferences that were set by an administrator (it is read-only,
so this layer is unavoidable).
- In extensions/chromium/options/migration.js, similar logic is
added, except in this case the preference storage is writable,
so this migration logic happens only once.
The "enhanced text selection" mode is still experimental, so it
has been marked as experimental to signal that there may be bugs.
The list of tasks that block promotion to stable is at #7584.
2018-02-16 18:02:05 +01:00
|
|
|
if (!chrome.runtime.lastError) {
|
|
|
|
storageSync.remove([
|
|
|
|
"disableTextLayer",
|
|
|
|
"enhanceTextSelection",
|
|
|
|
]);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
);
|
|
|
|
} else {
|
|
|
|
storageSync.remove(["disableTextLayer", "enhanceTextSelection"]);
|
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 15:59:37 +01:00
|
|
|
}
|
[CRX] Make textLayerMode pref visible and add migration logic
In a1cfa5f4d7c8fcf55e9f3b51a23885dca8782915, the textLayerMode
preference was introduced, to replace the disableTextLayer and
enhanceTextSelection preferences.
As a result, the text selection preference was no longer visible
in Chrome (because preferences are only rendered by default for
boolean preferences, not for enumerations).
This commit adds the necessary bits to
extensions/chromium/options/options.{html,js}
so that the textLayerMode preference can be changed again.
Also, migration logic has been added to move over preferences
from the old to the new names:
- In web/chromecom.js, the logic is added to translate
preferences that were set by an administrator (it is read-only,
so this layer is unavoidable).
- In extensions/chromium/options/migration.js, similar logic is
added, except in this case the preference storage is writable,
so this migration logic happens only once.
The "enhanced text selection" mode is still experimental, so it
has been marked as experimental to signal that there may be bugs.
The list of tasks that block promotion to stable is at #7584.
2018-02-16 18:02:05 +01:00
|
|
|
}
|
2019-02-02 10:08:45 +01:00
|
|
|
// Migration code for https://github.com/mozilla/pdf.js/pull/10502.
|
|
|
|
if (typeof items.showPreviousViewOnLoad === "boolean") {
|
|
|
|
if (!items.showPreviousViewOnLoad) {
|
|
|
|
storageSync.set(
|
|
|
|
{
|
|
|
|
viewOnLoad: 1,
|
|
|
|
},
|
2020-04-14 12:28:14 +02:00
|
|
|
function () {
|
2019-02-02 10:08:45 +01:00
|
|
|
if (!chrome.runtime.lastError) {
|
|
|
|
storageSync.remove([
|
|
|
|
"showPreviousViewOnLoad",
|
|
|
|
"disablePageMode",
|
|
|
|
]);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
);
|
|
|
|
} else {
|
|
|
|
storageSync.remove(["showPreviousViewOnLoad", "disablePageMode"]);
|
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 15:59:37 +01:00
|
|
|
}
|
2019-02-02 10:08:45 +01:00
|
|
|
}
|
|
|
|
}
|
2017-07-15 01:50:15 +02:00
|
|
|
);
|
|
|
|
}
|
2024-09-02 01:34:25 +02:00
|
|
|
});
|