probablyrobert
Joined 5 years ago
Joined 5 years ago
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.
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.
Firefox Sync does work!
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 personally prefer non-smooth scrolling as it feels faster.
I don't think it'll be possible to implement multi-cursor support through the config though unfortunately.
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.
[0]: https://github.com/glide-browser/glide/blob/8171c5c2af000b71...
I've used it to add keymappings so that hints only apply to certain kinds of buttons on a page, e.g. https://github.com/RobertCraigie/dotfiles/blob/ecfd6f66e8a77...
I'm currently actually tracking the firefox beta channel because the frequent small updates are so easy to do.