akira/pdfjs-dist - pdfjs-dist - Gitea: Git with a cup of tea

Tree: 6048c8a910

Author	SHA1	Message	Date
Rob Wu	1055350425	Chrome extension: Isolate pageAction logic Remove pageAction logic from extension router, and put it in a separate file. The pageAction URL parsing logic has been simplified, and all pageAction-related files have been moved to a separate directory.	11 years ago
Rob Wu	a1671fa512	Preserve reference fragment in Chromium URL router Because removed reference fragments are no longer automatically copied thanks to https://code.google.com/p/chromium/issues/detail?id=354653	11 years ago
Tim van der Meij	8d2068dc6f	Making extensions/chromium/extension-router.js adhere to the style guide	11 years ago
Rob Wu	60fb28caf0	Register as File browser handler in Chrome OS	11 years ago
Rob Wu	aeaf11ca43	[CRX] Fall back to sender.tab.url if !tab.url sender.url is relatively new (Chromium 29) ( https://chromiumcodereview.appspot.com/14301016 )	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