Make vimium work in Chrome WebStore and PDF viewer

[jefferyyuan]

• I know this has been requested by others before, but just noticed that The Great Suspender works for all tabs: WebStore, pdf viewer.
• Maybe it's possible to also make vimium work in Chrome WebStore and PDF viewer?
• Checked the difference between permission request by Suspender and vimium.
• Suspender:
  • https://github.com/deanoemcke/thegreatsuspender/blob/master/src/manifest.json

    "http://*/*",
    "https://*/*",
    "file://*/*",

• vimium

  "<all_urls>"

• Doesn't know whether this will make a difference, but it would be great if vimium can work everywhere (Use it a lot every day) !!!
  • Also PDF Viewer for Vimium C says: it works with pdf viewer

[gdh1995]

Currently there's no API from Chrome to allow this.

The reason that "The Great Suspender" works is that it does not execute operations on the PDF "content", while Vimium needs. On a timer gets triggered, the suspender replaces the PDF (or Web Store) tab with one of its inner page, and then replace back when you click the page.

As for the "Vimium C", it's one of my personal extensions which is a customized version of Vimium, and the "PDF Viewer for Vimium C" is a special PDF viewer extension, which is NOT OFFICIAL, compiled from https://github.com/mozilla/pdf.js and with some modification. So, it's still not the case that an extension runs on Chrome's inner PDF viewer.

BTW, on Chrome, its default PDF viewer, chrome://* pages and the Chrome Web Store are privileged and no 3rd-party extensions can run on them. On Firefox, there's an extra limit that webextensions can't create a tab of about:* (except about:blank) or file:///*.

[mrjared16]

Currently there's no API from Chrome to allow this.

The reason that "The Great Suspender" works is that it does not execute operations on the PDF "content", while Vimium needs. On a timer gets triggered, the suspender replaces the PDF (or Web Store) tab with one of its inner page, and then replace back when you click the page.

As for the "Vimium C", it's one of my personal extensions which is a customized version of Vimium, and the "PDF Viewer for Vimium C" is a special PDF viewer extension, which is NOT OFFICIAL, compiled from https://github.com/mozilla/pdf.js and with some modification. So, it's still not the case that an extension runs on Chrome's inner PDF viewer.

BTW, on Chrome, its default PDF viewer, chrome://* pages and the Chrome Web Store are privileged and no 3rd-party extensions can run on them. On Firefox, there's an extra limit that webextensions can't create a tab of about:* (except about:blank) or file:///*.

What is the difference between your Extension to Vimium? I install both on Opera and the extension doesn't work on Google.com, which is a huge inconvenience for me. Other extensions cannot work too. Does it cause by Opera or the Chromium API reason? Can I personally modify the source to make it work just for me?

[gdh1995]

This Vimium is a stable browser extension, while my Vimium C is modified from Vimium, with more commands and features (also more bugs). I've tested it on Opera, so I'll have a test in recent days.

[gdh1995]

@mrjared16 the probem that many extension can not run on google.com on Opera is beacuse:

• Opera has a particular option "Allow access to search page results" to control whether an extension can run on google.com
• and this option is turned off by default, you have to turn on it for every extension you want
• although its name has "aceess to search page results", in fact Opera only applies such a limit on google search result pages.
• Even when your default search engine is not Google, the limit still exists and only exists on google.com.

[mrjared16]

@mrjared16 the probem that many extension can not run on google.com on Opera is beacuse:

• Opera has a particular option "Allow access to search page results" to control whether an extension can run on google.com
• and this option is turned off by default, you have to turn on it for every extension you want
• although its name has "aceess to search page results", in fact Opera only applies such a limit on google search result pages.
• Even when your default search engine is not Google, the limit still exists and only exists on google.com.

You are my hero. Thank you!

[nusssreiner]

Maybe there is a way to just redirect keys while in the pdf viewer? I don't know how scrolling is embedded, but maybe it is possible to just implement that pressing j or k in the PDF viewer corresponds to pressing arrow keys? And that HJKL corresponds to pressing Alt+tab, Ctrl+tab, Ctrl+shift+tab, Alt+shift+tab. That way only these few commands would work but that would be fine for many users, since getting away from pdf tabs and scrolling through pdfs are the most needed features in this situation