Shameless shill - I found Tridactyl and Vimium to be frustratingly limited due to the security restrictions imposed on web extensions, so I've been working on https://glide-browser.app/ for a while; It's a fork of Firefox with (some) vim motions and a TypeScript based config.
Thank you! I just implemented the ones I use the most, e.g. diw, but the motions system is still in very early stages and there are lots of motions I haven't implemented yet.
I do plan on implementing as many motions as is feasible, but there are some intentional differences, e.g. `f` is used for hints instead of jump-to-char.
I'm not entirely sure what is going to happen with imports to be honest. My current thinking is that they'll be supported eventually but that imported modules should not have access to glide APIs. For anything that does need to use glide APIs, I would support that through a separate API.
Yes eval is blocked, and extensions / websites cannot access glide APIs.
Thanks that is very helpful! Agree those things should be mentioned in the security doc.
RPC is not currently supported but I agree it would be pretty interesting, tweety[0] was recently shared with me and that looks like it'd be quite nice, although I haven't tried it yet.
So far the only divergence from Firefox that could impact security is evaluating the config file, so I've described how that is sandboxed in the security[1] docs but I'm not super happy with the contents of that docs page; anything else you'd like to see mentioned?
I'm not very familiar with Helix keybindings myself but if there are vim equivalents (and if they're actually implemented, a fair amount of mappings are missing right now) then you should be able to! There's a `motion` excmd you can use in your mappings.
I don't think it'll be possible to implement multi-cursor support through the config though unfortunately.
ah yeah sorry about that, the API docs aren't quite complete yet.
I'd recommend just looking at the glide.d.ts[0], it should be pretty readable (I hope).
Yes the TS API supports it as well with the `selector` property:
```
glide.hints.show({ selector: "..." });
```
> Also, would you consider making it return a promise instead of taking a callback? I think that would be more ergonomic.
The reason it doesn't return a Promise directly is because the hints that are generated are not static, try scrolling while hints are active and you'll see them refresh.
So the return type would have to be something else to work well with this functionality imo.
It's implemented as a set of patches + new files for net new files I add myself, then to build it, the firefox source is downloaded and patched automatically - so bumping the underlying firefox version is generally very easy.
I'm currently actually tracking the firefox beta channel because the frequent small updates are so easy to do.