I’m in Chrome, Ubuntu. I got the extension years ago from the marketplace (and I love it). It’s called Type-ahead-find.
Simple keys. In a list of issues it’s j/k to go forward/back, e to edit, l (lower-case L) to edit labels, c to create, …
In looking at the docs (which I haven’t done in literally years) it seems that I can blacklist sites. So… I’ve blacklisted and reloaded the window and it still has no effect (with nothing in the console). I’ll try restarting the browser…
Wow! It seems the only way to “select” a post is to “browse” to it using j/k. If I click a post a dozen times it does nothing. It’s only when I use the keyboard that the red selection indicator is added to the interface! Since I wasn’t aware of the keyboard shortcuts it never occurred to me to use the keyboard in this interface. I’ve never seen the red selection indicator before just now.
May I suggest that this facet of the UX be reconsidered?
I’m coming back to this because the UI continues to surprise.
I’m scrolled to the bottom of the first/only post in a thread. I want to edit it. My hands are on the keyboard, so I hit ‘j’ to select it and the first post in the list of ‘other topics’ gets the red border instead. So… in some implicit yet unusable way, the thread post was already selected?
Actually, I was quite surprised by the way that one worked. For very short posts - where I can see the buttons and a good bit of the ‘Suggested’ list on first page load, ‘j’ selects the OP. Here’s a medium-length example: