pdfjs-dist

Tree: ca61ccc533

Author	SHA1	Message	Date
Rob Wu	94ba01c8aa	Use tab-specific stream storage Also: - Use webNavigation.getAllFrames to find out whether the navigation has already started. This is (at least) needed for top-level navigation to a stream. The webNavigation.onErrorOccurred event has become obsolete, and has been removed.	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	18e4d32c11	Update chrome.tabs.executeScriptInFrame dependency References: - https://github.com/Rob--W/chrome-api/issues/1 - `4c5a598c0b...f211d2d679`	11 years ago
fkaelberer	1b35bf6c5e	Recompressed PNG assets	11 years ago
Rob Wu	ac8b8079a4	Added missing <html> tag to page action	11 years ago
Rob Wu	e20bc529c8	Remove superfluos <!DOCTYPE html> from page action Fixes #4064	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	91dd664732	[CRX] Reload extension tab after session restore	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	e9cb91de39	[CRX] split:incognito is used, so update file:-handler The current stable Chromium version is 29. Since the critical bug that prevented use of incognito:split has been fixed, and incognito:split is actually used, it's safe to drop the code that disables the extension in incognito mode. ( fixed bug = http:/crbug.com/224094 )	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
Rob Wu	820b95416b	chrome.runtime -> chrome.extension when needed Some Ubuntu users are still stuck at Chromium 25.	12 years ago
Rob Wu	6070a37788	chrome.extension -> chrome.runtime for Ubuntu Addresses issue #3800, where a bug specific to Ubuntu builds of Chromium break PDF.js https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1232575	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

1 2

76 Commits (ca61ccc533ab9e0d693d32cec2c27ca9e7aabdd7)