k2nr / ViChrome

vi like key binds for Google Chrome
231 stars 40 forks source link

GoSearchModeForward not accessible from '/' key #20

Open lebels opened 13 years ago

lebels commented 13 years ago

Typing '/' doesn't enter GoSearchModeForward, it enters GoSearchModeBackward.

GoSearchModeBackward is broken, i.e. it doesn't show the number of results nor is it possible to navigate results using 'n' and 'N' keys.

k2nr commented 13 years ago

Typing '/' doesn't enter GoSearchModeForward, it enters GoSearchModeBackward.

please tell me

as Vichrome doesn't work properly if you're using Win/Linux and your country setting isn't US/Japanese due to the webkit issue.see https://bugs.webkit.org/show_bug.cgi?id=19906

GoSearchModeBackward is broken, i.e. it doesn't show the number of results nor is it possible to navigate results using 'n' and 'N' keys.

thanks.will be fixed in next release.

lebels commented 13 years ago

Fedora 16 - XFCE / Windows 7 Pro en_CA fr_CA

On 2011-11-17, at 22:02, Kazu reply@reply.github.com wrote:

Typing '/' doesn't enter GoSearchModeForward, it enters GoSearchModeBackward.

please tell me

  • what OS you are using
  • your PC's country setting
  • your PC's keyboard setting

as Vichrome doesn't work properly if you're using Win/Linux and your country setting isn't US/Japanese due to the webkit issue.see https://bugs.webkit.org/show_bug.cgi?id=19906

GoSearchModeBackward is broken, i.e. it doesn't show the number of results nor is it possible to navigate results using 'n' and 'N' keys.

thanks.will be fixed in next release.


Reply to this email directly or view it on GitHub: https://github.com/k2nr/ViChrome/issues/20#issuecomment-2785238

k2nr commented 13 years ago

maybe that's the cause.Currently Vichrome only supports en_US and ja_JP and I have no plan to support other language unless webkit fix the issue. To summarise, Vichrome only supports

The source file is coffee/key.coffee I'm waiting for your pull request!

Thanks,

klaernie commented 10 years ago

It seems like the webkit bug got fixed without any notice in the bugreport. At least Chrome/33.0.1750.154 works according to the testpage linked in the bugreport.