search

philc / vimium

The hacker's browser.
https://chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb
MIT License
23.51k stars 2.49k forks source link

generally not working #1296

Closed githubdbes1 closed 9 years ago

githubdbes1 commented 9 years ago

Hi All,

I just installed Vimium. Thank you to everyone who's worked on this project.

Unfortunately, it seems like Vimium won't work on most web pages I visit. If I type Shift-F nothing happens. I wonder if maybe there is a conflict with one of the other extensions I have installed? Below is a listing of those extensions in case someone spots one they know is problematic. Otherwise, are there any recommendations on preliminary things to investigate when Vimium isn't working?

Thanks, david

Windows 7 Pro SP1 64-bit Chromium 37 Portable details: +++++ User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.3 Safari/537.36

Extensions: 48

Disabled Extensions: 0

Exported with Share Extensions for Google Chrome™ - https://chrome.google.com/webstore/detail/chdafcbnfkfenoeejpaeenpdamhmalhe +++++

mrmr1993 commented 9 years ago

Can you check whether the extension is receiving the keypress for us?

Now, every time you press the F key on a page, a line that says "checking keyqueue: [F]" will come up if Vimium receives the key.

gmcm17 commented 9 years ago

I am having the same problems; Vivium is not working on any webpage for me in Chrome. I am a Mac user, OS 10.9.5. I followed the suggestions given by mrmr1993. Vivium is still not working. I get the following message in the console drawer when I press the "f" key on a page:

checking keyQueue: [ <m-> ] main.js:645 new KeyQueue: main.js:643 checking keyQueue: [ <m-> ] main.js:645 new KeyQueue: main.js:643 checking keyQueue: [ <m-`> ] main.js:645 new KeyQueue: extensions::sendRequest:82 Unchecked runtime.lastError while running tabs.insertCSS: Cannot access a chrome:// URL at chrome-extension://dbepggeogbaibhgnhhndojpepiihcmeb/background_scripts/main.js:482:17

Like githubdbes1, I also believe Vivium and one of my other extensions are not behaving well together. My Chrome extensions are given below; I notice that Tabs Outliner v0.4.81 is a common extension.

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36

Extensions: 28

Disabled Extensions: 12

Apps: 12

Exported with Share Extensions for Google Chrome™ -

mrmr1993 commented 9 years ago

Thanks @gmcm17! Has this just started happening for you since the last Chrome update?

Presumably you pressed the f key 3 times to get those messages? It looks as if our keycode handling has gone screwy if it's not showing a key being detected. To check that this is right could you test Vimium in a new Chrome profile? (You can leave your current chrome running :smile:)

After you're done with that, you can happily delete the directory you created. I'll also set up a small testbed with some of our utility functions to see if they're the problem, in case a fresh profile doesn't help.

mrmr1993 commented 9 years ago

I've set up a minimal test here. Pressing the f key should result in

keydown: f
keypress: f

if Vimium is working correctly. You may have to click in the main window to activate it, and possibly enter Vimium's insert mode (press i) before the script starts recognising keystrokes.

gmcm17 commented 9 years ago

Thank you mrmr1993.

I set up a new directory and new profile for Chrome and then downloaded Vimium. It worked fine. I deleted the new directory, quit Chrome, then reopened it with my default profile. Vimium worked fine. I probably should have just quit and reopened Chrome to begin with instead of troubling you. Thank you for your help.

gmcm17 commented 9 years ago

mrmr1993.

To answer your question, yes, this problem arose with the last Chrome update.

mrmr1993 commented 9 years ago

Ahh, the old turn-it-off-and-on-again. I hadn't thought of that either! Thanks for helping me try to debug, though :)

@githubdbes1 does restarting Chrome do anything for you?

githubdbes1 commented 9 years ago

mrmr1993 wrote:

Can you check whether the extension is receiving the keypress for us?

Sometimes it does, sometimes it does not, and occasionally an error is thrown. This time (with the Dev Tools Console open) functionality of Vimium seemed to progressively degrade the more I pressed Shift-F. So much that I disabled it. Unfortunately when I disabled it I didn't realize the Developer Tools Console would close (and the messages I had generated too, before I had copied them).

There did seem to be certain websites that were more problematic than others. On github.com, google.com, and blekko.com (another search engine) Vimium Shift-F would fail to function at least 50% of the time.

-- david

githubdbes1 commented 9 years ago

mrmr1993

@githubdbes1 does restarting Chrome do anything for you?

I'm in the middle of a bunch of work (I installed Vimium to help me work faster) and have not restarted Chromium since installing Vimium. I'll see if I can make time to restart tonight.

-- david

smblott-github commented 9 years ago

@githubdbes1. Any further problems?

maheshsundaram commented 9 years ago

I have been using Vimium sucessfully until.. just a day ago? It seems that it was recently updated? I recall seeing a tiny popup stating that it was updated though I don't remember if that is when I began having problems.

I am using Chromium 37.0.2062.120 Built on Ubuntu 14.04, running on LinuxMint 17

I only have 2 extensions installed and enabled, AdBlock 2.15 and Vimium 1.48.

The problem for me is that none of the scrolling keys seem to do anything anymore. j, k, l, h, gg, G... but for example, ? and f work.


new KeyQueue:  main.js:722
checking keyQueue: [ k ] main.js:720
new KeyQueue:  main.js:722
checking keyQueue: [ G ] main.js:720
new KeyQueue:  main.js:722
checking keyQueue: [ g ] main.js:720
new KeyQueue: 1g main.js:722
checking keyQueue: [ 1gg ] main.js:720   <-- this results from pressing 'gg'
new KeyQueue:  main.js:722
checking keyQueue: [ f ] main.js:720 <-- so far the only key that works
new KeyQueue:
smblott-github commented 9 years ago

I am using Chromium 37.0.2062.120 Built on Ubuntu 14.04, running on LinuxMint 17

@fivepeakwisdom: Your problem should be fixed in 1.49.

smblott-github commented 9 years ago

@githubdbes1: Are you still having problems?

gmcm17 commented 9 years ago

A restart of Chrome worked for me.

On Tuesday, December 16, 2014 at 11:49 PM, Stephen Blott wrote:

@githubdbes1 (https://github.com/githubdbes1): Are you still having problems?

— Reply to this email directly or view it on GitHub (https://github.com/philc/vimium/issues/1296#issuecomment-67287654).

smblott-github commented 9 years ago

Closing, assuming fixed. @githubdbes1: Reopen if you're still having problems.