Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
520fdf2f6a
pdf.js/extensions/chromium/manifest.json

53 lines
1.0 KiB
JSON
Raw Normal View History

Initial Chrome extension import
2011-10-19 02:43:43 +09:00
{
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-06 14:52:17 +09:00
"manifest_version": 2,
Changes to allowed versioned building of Chrome extension that meets new Chrome extension security requirements
2012-09-07 00:33:07 +09: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-22 01:11:35 +09:00
"description": "Uses HTML5 to display PDF files directly in the browser.",
Add icons to the Chrome extensions
2013-02-17 11:15:01 +09:00
"icons": {
"128": "icon128.png",
"48": "icon48.png",
"16": "icon16.png"
},
Initial Chrome extension import
2011-10-19 02:43:43 +09:00
"permissions": [
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-14 04:23:31 +09:00
"webRequest", "webRequestBlocking",
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 07:28:45 +09:00
"<all_urls>",
[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-18 01:57:18 +09: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-14 01:28:13 +09:00
"webNavigation",
Work-around for http://crbug.com/276898 When a new incognito session is started, the onExecuteMimeTypeHandler event is often not dispatched in time. Instead, it's triggered in the non-incognito profile. This commit offers a work-around that allows new incognito instances to view PDF files.
2013-08-22 01:37:22 +09:00
"storage",
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-14 01:28:13 +09:00
"streamsPrivate"
Initial Chrome extension import
2011-10-19 02:43:43 +09:00
],
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 07:28:45 +09:00
"content_scripts": [{
Insert dummy content script at every location. This is needed for propagating the extension's permissions to the extension's iframe, in the rare event that the PDF is loaded in a sub frame, and the extension does not have access to the top frame. For instance, when a http:-PDF file is embedded in a local file, while "Allow access to local URLs" is disabled. Note: Propagating permissions by inserting content scripts is an undocumented feature (http://crbug.com/302548). Whenever it breaks, the issue (cross-domain permissions for XHR) can be solved by using a content script that gets the blob using the XMLHttpRequest API, followed by `postMessage` (via transferables) to efficiently pass the arraybuffer back to the PDF Viewer.
2013-12-05 19:16:14 +09:00
"matches": [
"http://*/*",
"https://*/*",
"ftp://*/*",
"file://*/*"
],
[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-02 05:16:28 +09:00
"js": ["nothing.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 07:28:45 +09:00
}],
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-14 01:28:13 +09:00
"mime_types": [
"application/pdf"
],
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-06 14:52:17 +09:00
"background": {
"page": "pdfHandler.html"
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 07:28:45 +09:00
},
[CRX] Add a pageAction to omnibox showing PDF URL In Chromium extensions, the viewer's URL looks like this: chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/http://example.com/file.pdf Furthermore, the PDF Viewer itself can also add something to the reference fragment: chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/http://example.com/file.pdf#page=2 Consequently, it is difficult to copy a clean URL (e.g. for sharing over mail) without having to tidy-up the URL manually. This commit solves this issue by adding a button to the omnibox, which shows the clean PDF URL on click.
2013-12-07 20:32:08 +09:00
"page_action": {
"default_icon": {
"19": "icon19.png",
"38": "icon38.png"
},
"default_title": "Show PDF URL",
"default_popup": "pageActionPopup.html"
},
[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-02 05:16:28 +09: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 07:28:45 +09:00
"web_accessible_resources": [
[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-02 05:16:28 +09:00
"getFrameId",
[CRX] Show nicely formatted URL in omnibox Before commit: chrome-extension://EXTENSIONID/content/web/viewer.html?file=http%3A%2F%2Fexample.com%2Ffile.pdf After commit: chrome-extension://EXTENSIONID/http://example/file.pdf Technical details: - The extension's background page uses the webRequest API to intercept requests for <extension host>/<real path to pdf>, and redirect it to the viewer's URL. - viewer.js uses history.replaceState to rewrite the URL, so that it's easier for users to recognize and copy-paste URLs. - The fake paths /http:, /https:, /file:, etc. have been added to the web_accessible_resources section of the manifest file, in order to avoid seeing chrome-extension://invalid/ instead of the actual URL when using history back/forward to navigate from/to the PDF viewer. - Since the relative path resolving doesn't work because relative URLs are inaccurate, a <base> tag has been added. This method has already been proven to work in the Firefox add-on. Notes: - This commit has been cherry-picked from crx-using-streams-api. - Need to merge https://github.com/mozilla/pdf.js/pull/3582 to deal with a bug in Chrome <=30 - In Chrome, getting the contents of a FTP file is not possible, so there's no support for FTP files, even though the extension router recognizes the ftp: scheme.
2013-08-16 05:47:30 +09:00
"content/web/viewer.html",
"http:/*",
"https:/*",
"ftp:/*",
"file:/*",
"chrome-extension:/*"
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 07:28:45 +09:00
]
Initial Chrome extension import
2011-10-19 02:43:43 +09:00
}
Reference in New Issue Copy Permalink