chromium-vim icon indicating copy to clipboard operation
chromium-vim copied to clipboard

No cursor in command bar

Open carpetscheme opened this issue 6 years ago • 17 comments

Sometimes when I open the command bar with any kind of mapping, the cursor doesn't go into the command bar. This happens about half the time, not always. Then I must either close the bar with Esc and try opening it again, or mouse click in the bar, to type a command.

This only started a few days ago on Chrome Version 74.0.3729.58 (Official Build) beta (64-bit).

Thanks in advance and for a great extension!

carpetscheme avatar Apr 08 '19 07:04 carpetscheme

I'm having the same issue. I'm on 74.0.3729.40.

carlf avatar Apr 11 '19 16:04 carlf

I'm having the same issue since a couple of weeks. This also happens with the search box.

Pressing / doesn't focus the search box anymore (at least ~50% of the time).

Version: 74.0.3729.75 (Official Build) beta (64-bit).

0xC0FFEE avatar Apr 19 '19 16:04 0xC0FFEE

Same problem here. Exactly the same problem. My cvimrc: let locale = "de" set smoothscroll let scrollduration = 150 let scrollstep = 150 let completionengines = ["google", "amazon", "wikipedia","wolframalpha","youtube"] let searchalias g = "google" let searchalias w = "wikipedia" let searchalias a = "amazon" let searchalias c = "wolframalpha" let searchalias y = "youtube" set completeonopen map s :tabnew google<Space> map S :open google<Space> set noautofocus

rkunschke avatar May 02 '19 17:05 rkunschke

m2bump

257 avatar May 03 '19 16:05 257

// will get me into 'INSERT' if you like so i can type. same with o and t.

257 avatar May 03 '19 16:05 257

// will get me into 'INSERT' if you like so i can type. same with o and t.

For me this only works half of the time, the other half I end up with an unwanted / in the search box (same is true for o and t too).

Edit: Might be related to this issue[1] in Vimium. A race condition could definitely explain the flaky behavior. FWICT the setTimeout-trick is already used in cVim; at least sometimes[2]?

[1] https://github.com/philc/vimium/issues/3242 [2] https://github.com/1995eaton/chromium-vim/blob/fe60f5fa18e5f6ec379494c346127a221307aff7/content_scripts/command.js#L943-L944

0xC0FFEE avatar May 03 '19 17:05 0xC0FFEE

Also having this problem since the last Chromium update (now on 74.0.3729.131, don't know what the previous version was.)

bernieke avatar May 11 '19 07:05 bernieke

I fixed 1 line and add 1 line as follows, then the problem is solved. However, I don't think this is the correct method. https://github.com/1995eaton/chromium-vim/blob/283ec275ce3b20e7de991cbb64cb7758e4442661/content_scripts/command.js#L943-L944

-  setTimeout(function() {
+  var timerId = setInterval(function() {

https://github.com/1995eaton/chromium-vim/blob/283ec275ce3b20e7de991cbb64cb7758e4442661/content_scripts/command.js#L956-L957

       document.getSelection().modify('move', 'right', 'lineboundary');
+      clearInterval(timerId);

asmka avatar May 18 '19 15:05 asmka

Above workaround works fine for me.

  • Chrome 74.0.3729.169
  • macOS 10.14.3 (Mojave)

@dff9th thanks!

ottijp avatar May 31 '19 04:05 ottijp

Works for me too!

bernieke avatar May 31 '19 04:05 bernieke

@dff9th thank you.

monkoose avatar Jun 08 '19 17:06 monkoose

@dff9th works!

cuppajoeman avatar Jun 11 '19 16:06 cuppajoeman

@dff9th Works for me. Thank you. 背に腹はかえられません。

mosakabe avatar Jun 17 '19 11:06 mosakabe

@basyura I see that this change has been made, but I'm still having the problem. Is it because I added the cVim extension through the store instead of getting it directly from github?

barucharky avatar Jun 26 '19 21:06 barucharky

@dff9th Works for me. Thank you.

jessewkun avatar Sep 05 '19 02:09 jessewkun

@dff9th Unfortunatly the workaround did not worked for me, still having the same issue. Using Brave 1.0.1 with Chromium 78.0.3904.108

skaaj4 avatar Dec 26 '19 20:12 skaaj4

looks like #724 integrates tyybbi's code into it too. I cloned that, ran npm install && make, removed the extension and uploaded it via "load unpacked" according to the README way at the bottom. Until it gets merged & pushed to the Chrome store, we gotta do it the manual way. See #723 .

schmitmd avatar Feb 12 '20 02:02 schmitmd