5 ms·

Thank you for your work. I'm currently a tridactyl user. However I'd like to point out that none of these replacements can currently compete with the previous e

Thank you for your work. I'm currently a tridactyl user. However I'd like to point out that none of these replacements can currently compete with the previous extensions in term of usability. Simply put, you cannot count on the keyboard shortcuts to work consistently throughout Firefox. They do not work in built-in pages (such as errors). They do not work when inside an input field in GTK. There's no way to consistently override built-in FF shortcuts that simply get in the way. It's pretty sad for users which expect the keyboard experience to be consistent. I now mostly use FF's own shortcuts for most of the tab-management actions, since those are the only ones that work most of the time when an error page is generated.

bovine3dom 8y ago
Have you looked at xkeysnail [1]? I've heard it's OK but I haven't got around to trying it myself. Personally I just hit Ctrl-W to close tabs when I get to somewhere I can't use it. `fixamo` and `set csp clobber` mean that I only really ever get trapped in PDFs (as I rarely open about: pages except to do a specific thing and then immediately close them). [1] https://github.com/mooz/xkeysnail https://github.com/mooz/xkeysnail
buovjaga 8y ago
Relevant WebExtensions metabug: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 "Better keyboard shortcut support"
derefr 8y ago
> They do not work when inside an input field in GTK. I feel like this is a symptom of a larger issue: if Firefox is a GTK app (in Linux), why is it up to Firefox to decide how to resolve these inputs? Shouldn't it be GTK doing that? Ergo, shouldn't the "vi-ization" be occurring at the GTK level, and so apply to all GTK apps loaded by the user? > They do not work in built-in pages (such as errors). That's certainly dumb, though.
PurpleRamen 8y ago
Worse is the unreliable working of vi-keys. Often enough focus ends somewhere on the page, and the vi-extension just stops working. I've yet to find a reliable way to gain input-focus again in those cases.
- bovine3dom 8y ago
  Sometimes this is our fault - there's a bug with our command line where it doesn't close properly and can steal focus (particularly `tabopen about:addons`). I am sorry about that. We're working on tearing it out and starting again as the command line has lots of problems. Otherwise, it's usually YouTube. I just only interact with the videos using the mouse (or MPV via `;v`) and make sure to click outside them afterwards. I do have a trackpoint on all of my keyboards, so I don't really notice having to click the mouse because it's just another keyboard button, so I might not be the most representative person here.
  - PurpleRamen 8y ago
    I don't think it's just that bug. I have a userstyle to mark the displayed element, so I sometimes see when something is grabing the focus, and neither tab nor ESC or Alt-l helps in those cases. But after some reseach I found out F6 can help there. Till now I thought it's just the same as Alt-l and only focus the addressbar, but turns out it can also unfocus it and switch focus between the different areas of firefox. I tested it in the last hour and it really worked in several cases where I was stuck in focus-hell.

bovine3dom 8y ago

Have you looked at xkeysnail [1]? I've heard it's OK but I haven't got around to trying it myself. Personally I just hit Ctrl-W to close tabs when I get to somewhere I can't use it. `fixamo` and `set csp clobber` mean that I only really ever get trapped in PDFs (as I rarely open about: pages except to do a specific thing and then immediately close them). [1] https://github.com/mooz/xkeysnail https://github.com/mooz/xkeysnail

buovjaga 8y ago

Relevant WebExtensions metabug: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 "Better keyboard shortcut support"

derefr 8y ago

> They do not work when inside an input field in GTK. I feel like this is a symptom of a larger issue: if Firefox is a GTK app (in Linux), why is it up to Firefox to decide how to resolve these inputs? Shouldn't it be GTK doing that? Ergo, shouldn't the "vi-ization" be occurring at the GTK level, and so apply to all GTK apps loaded by the user? > They do not work in built-in pages (such as errors). That's certainly dumb, though.

PurpleRamen 8y ago

Worse is the unreliable working of vi-keys. Often enough focus ends somewhere on the page, and the vi-extension just stops working. I've yet to find a reliable way to gain input-focus again in those cases.

bovine3dom 8y ago
Sometimes this is our fault - there's a bug with our command line where it doesn't close properly and can steal focus (particularly `tabopen about:addons`). I am sorry about that. We're working on tearing it out and starting again as the command line has lots of problems. Otherwise, it's usually YouTube. I just only interact with the videos using the mouse (or MPV via `;v`) and make sure to click outside them afterwards. I do have a trackpoint on all of my keyboards, so I don't really notice having to click the mouse because it's just another keyboard button, so I might not be the most representative person here.
- PurpleRamen 8y ago
  I don't think it's just that bug. I have a userstyle to mark the displayed element, so I sometimes see when something is grabing the focus, and neither tab nor ESC or Alt-l helps in those cases. But after some reseach I found out F6 can help there. Till now I thought it's just the same as Alt-l and only focus the addressbar, but turns out it can also unfocus it and switch focus between the different areas of firefox. I tested it in the last hour and it really worked in several cases where I was stuck in focus-hell.