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

Tree: 50bd4a5ac0

Author	SHA1	Message	Date
Jonas Jenwald	4f48c8198c	Fix inconsistent spacing and trailing commas in objects in `extensions/` files, so we can enable the `comma-dangle` and `object-curly-spacing` ESLint rules later on http://eslint.org/docs/rules/comma-dangle http://eslint.org/docs/rules/object-curly-spacing Given that we currently have quite inconsistent object formatting, fixing this in in one big patch probably wouldn't be feasible (since I cannot imagine anyone wanting to review that); hence I've opted to try and do this piecewise instead. Please note: This patch was created automatically, using the ESLint `--fix` command line option. In a couple of places this caused lines to become too long, and I've fixed those manually; please refer to the interdiff below for the only hand-edits in this patch. ```diff diff --git a/extensions/firefox/content/PdfStreamConverter.jsm b/extensions/firefox/content/PdfStreamConverter.jsm index ea91a71a..0d59dad1 100644 --- a/extensions/firefox/content/PdfStreamConverter.jsm +++ b/extensions/firefox/content/PdfStreamConverter.jsm @@ -773,7 +773,8 @@ class RequestListener { response = function sendResponse(aResponse) { try { var listener = doc.createEvent("CustomEvent"); - let detail = Cu.cloneInto({ response: aResponse, }, doc.defaultView); + let detail = Cu.cloneInto({ response: aResponse, }, + doc.defaultView); listener.initCustomEvent("pdf.js.response", true, false, detail); return message.dispatchEvent(listener); } catch (e) { ```	8 years ago
Mark Banner	2e9ae50a3a	Use eslint-plugin-mozilla and the webextensions environment to avoid defining globals in each file.	8 years ago
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
Manas	a2ba1b8189	Uses editorconfig to maintain consistent coding styles Removes the following as they unnecessary /* -- Mode: Java; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -- / / vim: set shiftwidth=2 tabstop=2 autoindent cindent expandtab: */	10 years ago
Rob Wu	4ac8863e30	Restore extension tab after reload Work-around for https://crbug.com/511670	10 years ago
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