56e1d7746a
Originally the default preferences where simply placed in a JSON-file, checked into the repository, which over time became impractical, annoying, and error-prone to maintain; please see PR 10548. While that improved the overall situation a fair bit, it however inherited one quite unfortunate property of the old JSON-based solution[1]: It's still not possible for *different* build targets to specify their *own* default preference values. With some preferences, such as e.g. `enableScripting`, it's not inconceivable that you'd want to (at least) support build-specific default preference values. Currently that's not really possible, which is why this PR re-factors the default preferences generation to support this. --- [1] This fact isn't really clear from the `AppOptions` implementation, unless you're familiar with the `gulpfile.js` code, which could lead to some confusion for those new to this part of the code-base. |
||
|---|---|---|
| .. | ||
| content | ||
| tools | ||
| .eslintrc | ||
| README.mozilla | ||
This is the PDF.js project output, https://github.com/mozilla/pdf.js Current extension version is: PDFJSSCRIPT_VERSION Taken from upstream commit: PDFJSSCRIPT_COMMIT