3 ms·

It did not work well in Chrome: 36.0.1985.49 beta C-f, C-b didn't even work. I then gave it a shot in Firefox nightly and it seemed to work really well. This b

by markus2012 12y ago

It did not work well in Chrome: 36.0.1985.49 beta C-f, C-b didn't even work. I then gave it a shot in Firefox nightly and it seemed to work really well. This brings me joy. I don't like to edit forms/documents on the web; it's a constant struggle against my muscle memory. Vim.js could be the start of something that could change that. Well done!

gibbonsd1 12y ago
This doesn't work for me either. However, I am using the Vimium plugin for Chrome which may also cause issues.
- rifung 12y ago
  Did you try going into insert mode in vimium before trying it?
Sephr 12y ago
Chrome 36 beta came out half a year ago. It's unreasonable to expect web developers to support very old versions of a browser that silently auto-updates. Most popular frameworks and libraries, such as jQuery (see https://jquery.com/browser-support/ https://jquery.com/browser-support/), only officially support the latest stable Chrome and one version prior.
- deathanatos 12y ago
  (Edit: strike point about Chrome release date; had the release-release date, parent probably means when beta started.) I'll also note that in the past, I've purposefully not upgraded due to serious bugs in the present version of Chrome. (There was a great one a while ago where entire websites — notably Wikipedia — were rendering in the wrong font, for example.) > a browser that silently auto-updates While I'll grant that this is true for the majority of users: 1. It requires a user to restart their browser. For me, this usually means the next weekend or Chrome/OS X crash, since during the week I'm usually busy with things other than restarting the browser… 2. Not all OS's auto-update, though this is a very small minority.
- markus2012 12y ago
  It's unreasonable and unfair for you to assume I have any expectation for Vim.js to work with the version of Chrome I listed. I was merely providing feedback / datapoint.
- e12e 12y ago
  Right. So it eas pretty new in July, then? https://github.com/coolwanglu/vim.js/commits/master https://github.com/coolwanglu/vim.js/commits/master

gibbonsd1 12y ago

This doesn't work for me either. However, I am using the Vimium plugin for Chrome which may also cause issues.

rifung 12y ago
Did you try going into insert mode in vimium before trying it?

Sephr 12y ago

Chrome 36 beta came out half a year ago. It's unreasonable to expect web developers to support very old versions of a browser that silently auto-updates. Most popular frameworks and libraries, such as jQuery (see https://jquery.com/browser-support/ https://jquery.com/browser-support/), only officially support the latest stable Chrome and one version prior.

deathanatos 12y ago
(Edit: strike point about Chrome release date; had the release-release date, parent probably means when beta started.) I'll also note that in the past, I've purposefully not upgraded due to serious bugs in the present version of Chrome. (There was a great one a while ago where entire websites — notably Wikipedia — were rendering in the wrong font, for example.) > a browser that silently auto-updates While I'll grant that this is true for the majority of users: 1. It requires a user to restart their browser. For me, this usually means the next weekend or Chrome/OS X crash, since during the week I'm usually busy with things other than restarting the browser… 2. Not all OS's auto-update, though this is a very small minority.
markus2012 12y ago
It's unreasonable and unfair for you to assume I have any expectation for Vim.js to work with the version of Chrome I listed. I was merely providing feedback / datapoint.
e12e 12y ago
Right. So it eas pretty new in July, then? https://github.com/coolwanglu/vim.js/commits/master https://github.com/coolwanglu/vim.js/commits/master