vimium: Vimium is not working anymore after last update (2017/09/14)

Vimium suddenly stopped working for me as well.

Chromium | 49.0.2623.108 (Developer Build) Built on Ubuntu 14.04, running on Netrunner 14.1 (64-bit)
-- | --
Revision | d65a1c2f313b54fb0b90bb8a1082e4f5ecba2dda
OS | Linux
Blink | 537.36 (@d65a1c2f313b54fb0b90bb8a1082e4f5ecba2dda)
JavaScript | V8 4.9.385.33
Flash | 17.0.0.169
User Agent | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/49.0.2623.108 Chrome/49.0.2623.108 Safari/537.36
Command Line | /usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so --ppapi-flash-version=17.0.0.169 --enable-pinch --window-depth=24 --flag-switches-begin --enable-panels --flag-switches-end
Executable Path | /usr/lib/chromium-browser/chromium-browser
Profile Path | /home/alec/.config/chromium/Default
Variations | 16e0dd70-3f4a17dff19a86b5-55d854e7cf5ed6e1-3f4a17df775ebbd7-3f4a17df4ea303a6-3f4a17dffa99bb73-3f4a17dfdbffab5d-f51b51c8b9b12d-d93a0620867c4c68-3f4a17df

I restored vimium functionality (( it works! )) by:

1. git clone git@github.com:philc/vimium.git (can be anywhere, then you select it in step 4.c)
2. cd vimium
3. git checkout v1.59
4. cake build
5. enable it! a) in browser go to chrome://extensions/ b) enable developer mode c) load unpacked extension

@durann does something like that get it working for you?

ps: between steps 2 & 3 I had to sudo npm install --global coffeescript, which requires npm which I probably struggled to install a few years ago but apparently it seems to work right now 😉

D’oh. Just noticed the Chrome versions in the earlier comments. They are over 10 versions out of date, and don’t support KeyboardEvent.key, so our new key handling doesn’t work.

I recommend that you upgrade your Chrome installations.

@ahillio would you be able to do a git bisect to help us find which commit broke things for you?

Since chrome extensions don’t have a first party data model for declaring compatibility with chrome versions, I wonder if we should show a warning in the Vimium options page for versions of chrome which are known to be unsupported. This may be worthwhile to reduce the chance of noisy issues like this. In retrospect, this looks like this thread cost us a few hours of developer time.

What do you guys think?

On Sun, Sep 17, 2017 at 11:07 AM, ahillio notifications@github.com wrote:

Sweet, glad to stop fussing with the console log 😉

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/philc/vimium/issues/2646#issuecomment-330066608, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAhlt2LjRD2SQOAGGEPJAfICDpVFR2Jks5sjV_ZgaJpZM4PX30q .

1. git checkout v1.59

Does git checkout master (then cake build and reload in chrome://extensions, as usual) give you a non-functioning Vimium again?

• Thanks, but i am using Chromium unfortunately , as you can see from my post.

• it seems only way for Chromium is to change the update URL in manifest file of extension and point it to something useless (localhost for instance). What is pretty frustrating.

• besides, i have found that Show Advanced Options in the settings now. It is really intuitive. It is almost invisible on bottom of the setting page. Dont understand why this options should be hidden from users by default.

• in this Advanced Options a can found the new Ignore keyboard layout now. I can turn it on and off. But it is not helping anyhow. Vim keyboard shortcuts (j, k, d, u, f, anything) are still not working for me.

• after enabling Developer mode i found Inspect views: background page option below the extension. There was following url link chrome-extension://dbepggeogbaibhgnhhndojpepiihcmeb/pages/logging.html which displays something called Vimium Log. Unfortunatelly it displays nothing, no matter what i try to do with the Vimium (use it, enabling it, disabling it, trying to reload it in new page, whatever). I also enabled Collect errors option for the extension, but still, it displays nothing.

• i still need to find some way how to restore previous (working) version of the Vimium extension.