What is the crowd's opinion of Vim Vixen?

From 3.5 billion comments

>Won't fix the things that are already broken though.

most of stuff can be recreated for Photon, of course it requires work but you are not alone with that, most of people switched to Photon so there's more people working with it

>https://addons.mozilla.org/en-US/firefox/addon/smartup/ >https://addons.mozilla.org/en-US/firefox/addon/vim-vixen/ >https://addons.mozilla.org/en-US/firefox/addon/tab-session-manager/

nope, nope and nope

running these two as contentscripts causes a lot of performance overhead as cs has to be injected into every single frame, it doesn't allow extensions to interact with interface, it doesn't allow them to run on internal pages, extension pages and some mozilla pages (though afaik Alex is looking into this limitation), doesn't allow unbinding built in bindings

session API is still as poor as it was in 57 so it's not ready for daily use and has to evolve further

I don't deny that it's less than ideal, but we have a grace period and proper support, things Mozilla failed to provide. And on the other hand we can't stay with outdated Web Platform and barely working WebExtensions of 56, there are multiple important improvements and changes that came in these 11 versions that we should be looking forward for. But once again: if you are still not ready to switch you are free to stay with 56 for much longer and you will receive security updates (even though it requires a lot of extra work)

There's a new add-on, Vim Vixen which is way more Vimperator-alike. It has all the typical WebExtension downsides (won't work on internal pages etc) but at least it looks way better than Vimium. A friend of mine has been using Saka Key as a replacement.

If you really need Vimperator, ESR is your best bet until June next year.

When I used firefox vimium was my go to for vim binds. There are lots though and I'm sure that they are all fine. This seems to be popular.

<em>Tridactyl</em>, <em>Vim Vixen</em>, and <em>Vimium-FF</em> provide that functionality.

Why are chords anything fundamental? If an extension can bind one key, then it can maintain a small amount of state and implement chords like that (I mean, that's all the browser would have to do if it were to support this natively, which I don't think anyone cares about).

And there's quite a few extensions that do stuff like that and have "vim" there name; at least apparently hoping to be friendly to vim-users:

• https://addons.mozilla.org/en-US/firefox/addon/tridactyl-vim/
• https://addons.mozilla.org/en-US/firefox/addon/vim-vixen/
• https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/

Similarly, the concept of a prefix argument is nothing more than the concept of a particularly bit of (user-chosen) state. Why would web-extensions influence that at all? Firefox (and all other browsers on windows anyhow) does have the concept of e.g. paragraph selection; just triple-click. I'm sure other bindings could be made.

Most of this doesn't sound all that fundamental or even related to the old or new model; it just sounds like a lot of work to add on top of a platform that's pretty broad, extremely varied and simultaneously doesn't care about these features natively. It's all going to have to be in the extension; and that's bound to be a hassle. Perhaps there are some fundamental limitations (e.g. in accessing one extension from another), but you should be able to get usefully far; and judging the the extensions - some people try.

> Vimperator

In case it might help: people seem to use Saka Key or Vim Vixen nowadays. I don't use a Vim-like extension myself, so I don't know how good they actually are.

> the core browser is far more important than any extra functionality extensions add.

I only partially agree, which is why I compiled my own 57 with legacy add-on support. I literally cannot lose Tab Groups.

I'm trying to use https://addons.mozilla.org/en-US/firefox/addon/vim-vixen/ and it works mostly fine,

except that some pages hijack the entire ¤#%"¤% keyboard.

Like addons.mozilla.org.

For some reason not a single key makes it through to the addon, and is instead absorbed by the page somehow.

How do I forbid any page from creating any keyboard shortcuts whatsoever?