mirrors/pdf.js
1
0
Fork 0
mirror of https://github.com/mozilla/pdf.js.git synced 2025-04-19 14:48:08 +02:00
Code Activity
pdf.js/extensions/chromium/manifest.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

62 lines
1.4 KiB
JSON
Raw Permalink Normal View History

Initial Chrome extension import
2011-10-18 19:43:43 +02:00
{
[CRX] Bump minimum_chrome_version from 88 to 103 The minimum required version is Chrome 103 because wildcard support for web_accessible_resources[].extension_id was introduced in 103, in https://chromium.googlesource.com/chromium/src/+/c9caeb1a080f165f48d2a90559aa35d22965b440 A way to broaden compatibility is to drop that key. By doing so, the minimum required Chrome version is then 96, because of the chrome.storage.session API (and declarativeNetRequestWithHostAccess). Since gulpfile.js already defines "Chrome >= 98" and there is no real point in expanding support to older versions, I'm just setting the minimum version to 103.
2024-09-02 04:07:56 +02:00
"minimum_chrome_version": "103",
[CRX] Set manifest_version to 3 - Replace DOM-based pdfHandler.html (background page) with background.js (extension service worker). - Adjust logic of background scripts to account for the fact that the scripts can execute repeatedly during a browser session. Primarily, register relevant extension event handlers at the top level and use in-memory storage.session API to keep track of initialization state. - Extension URL router: replace blocking webRequest with the service worker-specific "fetch" event. - PDF detection: replace blocking webRequest with declarativeNetRequest. This requires Chrome 128+. The next commit will add a fallback for earlier Chrome versions.
2024-09-02 01:34:25 +02:00
"manifest_version": 3,
Changes to allowed versioned building of Chrome extension that meets new Chrome extension security requirements
2012-09-06 08:33:07 -07:00
"name": "PDF Viewer",
"version": "PDFJSSCRIPT_VERSION",
Renaming of extensions/chrome folder to extensions/chromium, and small tweak to manifest.json description as per #3600
2013-08-21 18:11:35 +02:00
"description": "Uses HTML5 to display PDF files directly in the browser.",
Add icons to the Chrome extensions
2013-02-16 23:15:01 -03:00
"icons": {
"128": "icon128.png",
"48": "icon48.png",
"16": "icon16.png"
},
Initial Chrome extension import
2011-10-18 19:43:43 +02:00
"permissions": [
[CRX] Replace localStorage in telemetry logic In MV3, the background script is a service worker. localStorage is not supported in service workers. Switch to storage.local instead. Data migration is not implemented because it is not needed due to the privacy-friendly design of the telemetry: In practice the data is reset about every 4 weeks, when the major version of Chrome is updated.
2024-09-01 22:54:49 +02:00
"alarms",
[CRX] Use DNR instead of webRequest in preserve-referer webRequestBlocking is unavailable in MV3. Non-blocking webRequest can still be used to detect the Referer, but we have to use declarativeNetRequest to change the Referer header as needed.
2024-09-01 01:02:13 +02:00
"declarativeNetRequestWithHostAccess",
Make chrome extensions compatible with latest API changes. That is, webRequest is no longer experimental and so it's easier to start (without --enable-experimental-extension-apis).
2012-02-13 20:23:31 +01:00
"webRequest",
[CRX] Improved navigation detection. A user reported that the PDF Viewer is not rendered on Dropbox, (Chrome on Mac OS X). This is apparently caused by the fact that the PDF file is loaded in an iframe in such a way that the tabs.onUpdated event is not triggered. This patch switches to the webNavigation event API, which improves the reliability of the navigation detection. Unfortunately Opera 15 does not support the webNavigation API, so the old (tabs.onUpdated) method is used (feature-detection is used, so whenever Opera decides to implement this API, it will profit from it).
2013-07-17 18:57:18 +02:00
"tabs",
Proof of concept using chrome.streamsPrivate API This method captures all application/pdf streams, loads the viewer and passes the stream to the PDF.js viewer. This commit shows a proof of concept using the chrome.streamsPrivate API. Advantages of new method: - Access to the response body of the original request, thus fewer network requests. - PDFs from non-GET requests (e.g. POST) are now supported. - FTP files are also supported. Possible improvements: - Use declared content scripts instead of dynamic chrome.tabs.executeScript. This allows the extension to render the viewer in frames when the extension is disallowed to run executeScript for the top URL. - Use chrome.declarativeWebRequest instead of webRequest, and replace background page with event page (don't forget to profile the difference & will the background/event page still work as intended?).
2013-08-13 18:28:13 +02:00
"webNavigation",
Remove streamsPrivate usage This was only ever useful for the Opera extension because the API requires a whitelisted extension ID. Opera ditched PDF.js from their extension gallery, so we don't need to keep this in the tree.
2016-05-09 22:49:47 +02:00
"storage"
Initial Chrome extension import
2011-10-18 19:43:43 +02:00
],
[CRX] Set manifest_version to 3 - Replace DOM-based pdfHandler.html (background page) with background.js (extension service worker). - Adjust logic of background scripts to account for the fact that the scripts can execute repeatedly during a browser session. Primarily, register relevant extension event handlers at the top level and use in-memory storage.session API to keep track of initialization state. - Extension URL router: replace blocking webRequest with the service worker-specific "fetch" event. - PDF detection: replace blocking webRequest with declarativeNetRequest. This requires Chrome 128+. The next commit will add a fallback for earlier Chrome versions.
2024-09-02 01:34:25 +02:00
"host_permissions": ["<all_urls>"],
Highly improved Chrome extension Full list feature changes in this commit: - Support for iframes - Switched to content-type (MIME) detection instead of hard-coding a case-sensitive check for the .PDF extension - The PDF's original URL is visible in the omnibox - Support for incognito mode Note: PDF viewer is disabled for the file:// + incognito combination, because it's currently impossible to get the combination to work. See https://github.com/mozilla/pdf.js/pull/3017#issuecomment-15693432
2013-04-04 00:28:45 +02:00
"content_scripts": [
{
[CRX] Remove obsolete manifest features In preparation for migrating the Chrome extension to Manifest Version 3, this patch removes parts of the manifest that are obsolete and/or unsupported in MV3. Remove ftp mentions: ftp was dropped from 6 years ago, in Chrome 59. Remove file_browser_handlers: does not work on Chrome OS according to https://github.com/mozilla/pdf.js/issues/14161 . MV3 replacement needs a different manifest key and logic, which will be added later. Remove content_security_policy: MV3 does not support unsafe-eval CSP, and PDF.js does not require it. This may result in a mild performance degradation in PDFs that contain PostScript. Remove page_action logic: When this logic was originally introduced, Chrome showed page action buttons in the address bar, which enabled the extension to display the button on specific PDF viewer tabs only. In Chrome 49 (2016), pageActions were dropped from the address bar and put in an UI area that is hidden by default. The user can pin the button to be unconditionally visible on the toolbar, which is distracting. Because the UX is no longer serving the original needs, this patch removes page_action from the manifest.
2024-08-25 20:34:03 +02:00
"matches": ["http://*/*", "https://*/*", "file://*/*"],
[CRX] Support <embed type="application/pdf">
2014-01-26 00:33:06 +01:00
"run_at": "document_start",
<object> / <embed> support in Chromium extension
2014-05-05 14:20:36 +02:00
"all_frames": true,
"css": ["contentstyle.css"],
[CRX] Support <embed type="application/pdf">
2014-01-26 00:33:06 +01:00
"js": ["contentscript.js"]
Highly improved Chrome extension Full list feature changes in this commit: - Support for iframes - Switched to content-type (MIME) detection instead of hard-coding a case-sensitive check for the .PDF extension - The PDF's original URL is visible in the omnibox - Support for incognito mode Note: PDF viewer is disabled for the file:// + incognito combination, because it's currently impossible to get the combination to work. See https://github.com/mozilla/pdf.js/pull/3017#issuecomment-15693432
2013-04-04 00:28:45 +02:00
}
],
[CRX] Enable WebAssembly in Chrome extension After the removal of 'unsafe-eval' CSP in #18651, WebAssembly fails to load, resulting in issues such as seen in #18457. Manifest Version 3 does not allow 'unsafe-eval', does accept the more specific 'wasm-unsafe-eval' as of Chrome 103. Note that manifest.json already sets minimum_chrome_version to 103. This patch also adds `object-src 'self'` because it was required until Chrome 110. As of Chrome 111, the default is `object-src 'self'` and `object-src` is no longer required. We could drop `object-src` in the future, but for now we need to include it to support Chrome 103 - 110.
2024-09-15 12:58:38 +02:00
"content_security_policy": {
"extension_pages": "script-src 'self' 'wasm-unsafe-eval'; object-src 'self'"
},
Managed preferences for Chrome administrators Implement support for managed preferences. This feature allows users (administrators) to easily change the default settings of the PDF Viewer for all Chrome or Chromium browsers within their organization. External resources for end users (administrators) - http://www.chromium.org/administrators/ - http://www.chromium.org/administrators/configuring-policy-for-extensions - http://www.chromium.org/administrators/windows-quick-start - http://www.chromium.org/administrators/mac-quick-start - http://www.chromium.org/administrators/linux-quick-start - http://www.chromium.org/administrators/policy-templates Administrators can read one of the previous links to learn more about creating policies. We want to auto-generate these templates, but there are no public tools for doing that. It will be added in the future, see: https://code.google.com/p/chromium/issues/detail?id=389061 Resources for PDF.js/extension developers - http://cs.chromium.org/file:policy_templates.json - https://developer.chrome.com/extensions/manifest/storage
2014-07-24 23:19:17 +02:00
"storage": {
"managed_schema": "preferences_schema.json"
},
Chrome extension: Add options page
2015-01-06 18:22:35 +01:00
"options_ui": {
[CRX] Drop chrome_style from manifest.json MV3 does not support chrome_style in options_ui. Remove it and replace it with the minimal amount of styles that still has some spacing around the individual settings for readability.
2024-09-01 20:38:47 +02:00
"page": "options/options.html"
Chrome extension: Add options page
2015-01-06 18:22:35 +01:00
},
"options_page": "options/options.html",
changes to allow chrome extension to load changes to remove inline scripts, update manifest version, fix make.js so compatibility.js isn't included for chrome. Due to new Chrome extension changes outlined at http://developer.chrome.com/extensions/manifestVersion.html
2012-09-05 22:52:17 -07:00
"background": {
[CRX] Set manifest_version to 3 - Replace DOM-based pdfHandler.html (background page) with background.js (extension service worker). - Adjust logic of background scripts to account for the fact that the scripts can execute repeatedly during a browser session. Primarily, register relevant extension event handlers at the top level and use in-memory storage.session API to keep track of initialization state. - Extension URL router: replace blocking webRequest with the service worker-specific "fetch" event. - PDF detection: replace blocking webRequest with declarativeNetRequest. This requires Chrome 128+. The next commit will add a fallback for earlier Chrome versions.
2024-09-02 01:34:25 +02:00
"service_worker": "background.js"
Highly improved Chrome extension Full list feature changes in this commit: - Support for iframes - Switched to content-type (MIME) detection instead of hard-coding a case-sensitive check for the .PDF extension - The PDF's original URL is visible in the omnibox - Support for incognito mode Note: PDF viewer is disabled for the file:// + incognito combination, because it's currently impossible to get the combination to work. See https://github.com/mozilla/pdf.js/pull/3017#issuecomment-15693432
2013-04-04 00:28:45 +02:00
},
[CRX] Change Viewer insertion method And use split incognito mode Previous method: - Rewrite content type to XHTML, followed by a content script to cancel and replace the document with the viewer. ( https://github.com/mozilla/pdf.js/pull/3017 ) New method: - Cancel loading of the document, followed by a redirect to the viewer Disadvantage of new method: - URLs are no longer "nice". This will be addressed by cherry-picking a commit from the crx-using-streams-api branch. Advantages of new method: - Idle time is minimal. In some cases (with large documents), it took too much time before the content script was activated. During this period, the page looked blank, and the contents of the PDF file were still retrieved and **discarded**. With the new method, the idle time is minimal, because the request is immediately cancelled. - No FOUXEP (Flash of unhidden XML error page), because the XHTML Content-Type hack is no longer used.
2013-10-01 22:16:28 +02:00
"incognito": "split",
Highly improved Chrome extension Full list feature changes in this commit: - Support for iframes - Switched to content-type (MIME) detection instead of hard-coding a case-sensitive check for the .PDF extension - The PDF's original URL is visible in the omnibox - Support for incognito mode Note: PDF viewer is disabled for the file:// + incognito combination, because it's currently impossible to get the combination to work. See https://github.com/mozilla/pdf.js/pull/3017#issuecomment-15693432
2013-04-04 00:28:45 +02:00
"web_accessible_resources": [
[CRX] Set manifest_version to 3 - Replace DOM-based pdfHandler.html (background page) with background.js (extension service worker). - Adjust logic of background scripts to account for the fact that the scripts can execute repeatedly during a browser session. Primarily, register relevant extension event handlers at the top level and use in-memory storage.session API to keep track of initialization state. - Extension URL router: replace blocking webRequest with the service worker-specific "fetch" event. - PDF detection: replace blocking webRequest with declarativeNetRequest. This requires Chrome 128+. The next commit will add a fallback for earlier Chrome versions.
2024-09-02 01:34:25 +02:00
{
"resources": [
"content/web/viewer.html",
"http:/*",
"https:/*",
"file:/*",
"chrome-extension:/*",
"blob:*",
"data:*",
"filesystem:/*",
"drive:*"
],
"matches": ["<all_urls>"],
"extension_ids": ["*"]
}
Highly improved Chrome extension Full list feature changes in this commit: - Support for iframes - Switched to content-type (MIME) detection instead of hard-coding a case-sensitive check for the .PDF extension - The PDF's original URL is visible in the omnibox - Support for incognito mode Note: PDF viewer is disabled for the file:// + incognito combination, because it's currently impossible to get the combination to work. See https://github.com/mozilla/pdf.js/pull/3017#issuecomment-15693432
2013-04-04 00:28:45 +02:00
]
Initial Chrome extension import
2011-10-18 19:43:43 +02:00
}
Copy permalink