pdfjs-dist

Commit Graph

Author	SHA1	Message	Date
Rob Wu	d9f90d595d	[CRX] Recognize blob and data-URLs in the router When a blob or data-URL is opened with the extension, viewer.html rewrites the URL. But when the viewer is refreshed (e.g. F5), Chrome would fail to display the viewer because the extension router was not set up to recognize such URLs. Now it is.	8 years ago
Rob Wu	9394fc133c	Remove support for frames in old Chromium versions Frames are only supported (via redirectUrl) in Chrome 35.0.1911.0+	9 years ago
Rob Wu	fc658a718c	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.	9 years ago
Rob Wu	1b043bfd5a	Chrome extension: Add options page	10 years ago
Rob Wu	00746011a3	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	11 years ago
Rob Wu	3fdd334a73	<object> / <embed> support in Chromium extension	11 years ago
Rob Wu	d126be9a61	Allow unsafe-eval to fix font renderer in crx Fixes #4660	11 years ago
Rob Wu	7f0fc8557e	[CRX] Support <embed type="application/pdf">	11 years ago
Rob Wu	60fb28caf0	Register as File browser handler in Chrome OS	11 years ago
Rob Wu	b754f9d878	Make streamsPrivate optional; remove manifest key Use streamsPrivate API when available. When the API is not available, the extension will still work on on http/https/file URLs, but not for POST requests or FTP. As of writing, the Chromium project has still not whitelisted the PDF Viewer extension in the Chrome Web Store. (extension ID oemmndcbldboiebfnladdacbdfmadadm) Request to whitelist PDF.js in Chromium: https://code.google.com/p/chromium/issues/detail?id=326949 Opera 19 has whitelisted the PDF Viewer extension from https://addons.opera.com/extensions/details/pdf-viewer/ (extension ID encfpfilknmenlmjemepncnlbbjlabkc) (https://github.com/Rob--W/pdf.js/issues/1#issuecomment-32357302) If you want to test the streamsPrivate feature in Chrome, edit the build/extensions/manifest.json and add the "key" again (see this commit for the value of this "key" field).	11 years ago
Rob Wu	af31ace940	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.	11 years ago
Rob Wu	32313b9149	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.	11 years ago
Rob Wu	cdadb0db4d	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?).	11 years ago
Rob Wu	8526d3c600	[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.	12 years ago
Rob Wu	83b780af81	[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.	12 years ago
Rob Wu	edd4bae903	[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.	12 years ago
Andreas Bovens	f2ad0f73d7	Renaming of extensions/chrome folder to extensions/chromium, and small tweak to manifest.json description as per #3600	12 years ago
Rob Wu	ec5ef58b84	[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).	12 years ago
Rob Wu	57e6238a6e	Enable Web Worker again in Chrome extension Previously, Web Workers were not created because of a security policy which does not respect relaxed privileges.	12 years ago
Rob Wu	e181a3c902	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	12 years ago
Aluísio Augusto Silva Gonçalves	d18f8d11bc	Add icons to the Chrome extensions	12 years ago
Michael Payne	05bca47b11	Include uppercase extensions for Chrome add uppercase case extension recognition for Chrome pdf.js	13 years ago
Michael Payne	6ca9245a39	Changes to allowed versioned building of Chrome extension that meets new Chrome extension security requirements	13 years ago
Michael Payne	088c6e17e8	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	13 years ago
Lucas Stadler	913faac2e4	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).	13 years ago
Vivien Nicolas	08af0c7686	Initial Chrome extension import	14 years ago

19 Commits (a63015a9a2dcd0145f9842cd62e35ce53e58bc1f)