L keyboard shortcut doesn't always work
-
Repro: Enter topic from link. Type 'l' (lower-case L) to like post.
Expected: Post's "like" state should toggle
Actual: No effect. L does not toggle like state until after J/K navigation. (Other navigation may also enable L; this is just what I tried.)
-
Expected: Post's "like" state should toggle
Which post?
The URL sometimes changes after entering a topic for example. And the post counter doesn't always represent the post indicated in the address bar.And even the 'current' post for J/K navigation is somewhat non-deterministic. For example clicking through to the last post of the (at the time fully read) LIkes thread and pressing J takes me to post 5857/5866
-
-
Which post? The URL sometimes changes after entering a topic for example.
I would expect the post pointed to by the link to toggle. No visible post toggles. I have the option set to not fuck with the URL while scrolling.
-
-
J/K seem to work as expected for me. Chrome/Windows 7. Well, except for one instance of crazy jitter.
-
J/K seem to work as expected for me. Chrome/Windows 7. Well, except for one instance of crazy jitter.
It works as designed. However, I still think it's FUBAR. I have to keep reminding myself that J is down and K is up, because it just feels backwards. Of course, W/S would have been a more logical, non-arrow choice for the many people used to ASDW navigation.
-
It works as designed. However, I still think it's FUBAR. I have to keep reminding myself that J is down and K is up, because it just feels backwards. Of course, W/S would have been a more logical, non-arrow choice for the many people used to ASDW navigation.
I have used J/K quite a bit in other places, but never here until this topic. You're right, it's backwards.
Reminds me of the shiftronic system in my car:
-
I have to keep reminding myself that J is down and K is up, because it just feels backwards.
As a vi/vim/gvim user for nigh on to 30 years, it seems perfectly natural to me. The idea of using vi keyboard navigation for a web forum, now that is a truly sick, twisted WTF.
-
I have used J/K quite a bit in other places, but never here until this topic. You're right, it's backwards.
Reminds me of the shiftronic system in my car:
WTF?! Why the hell would you want + to be down and - to be up?! That ... TDEMSYR!
-
One of the many reasons that I leave it in Drive.
-
As a vi/vim/gvim user for nigh on to 30 years, it seems perfectly natural to me. The idea of using vi keyboard navigation for a web forum, now that is a truly sick, twisted WTF.
Just like Jeff, you mean?
-
How else would you design a Future Thinking forum that breaks from the conventions of (boo! hiss!) traditional web forums, other than by using keyboard shortcuts from before the invention of arrow keys?
-
How else would you design a Future Thinking forum that breaks from the conventions of (boo! hiss!) traditional web forums, other than by using keyboard shortcuts from before the invention of arrow keys?
Well, duh, you use keyboard shortcuts from the future!
-
I have used J/K quite a bit in other places, but never here until this topic. You're right, it's backwards.
Are you sure about that? In vi(m), less, man pages (which I guess use less), the dearly-missed Google Reader, its substitute The Old Reader, Gmail, Google and DDG search results and who knows what else, it's always been j down and k up.
@chubertdev said:Reminds me of the shitronic system in my car:
As a European geek who's mostly seen only manual transmissions, it looks to me like your car has a Pseudo-Random Number Degenerator.<img src='/uploads/default/4459/77c3595ea7b3175d.jpg' alt="bass ackwards" />
PS: Disbugs likes to discard drafts if I don't write anything, even if I quote someone. Reading the rest of the thread before writing anything is Doing It Wrong, it seems.
-
Alternatively, it pays an homage to @PResideNtsDaughter
-
Disbugs likes to discard drafts if I don't write anything, even if I quote someone. Reading the rest of the thread before writing anything is Doing It Wrong, it seems.
No, that is actually the Atwood-approved way. But to Do It Not-Wrong, you must either start typing your reply or use only half your screen to read the rest of the topic, because collapsing an empty post is Doing It Wrong.
-
You're right, it only throws away the draft if I collapse. And I don't even have to scroll, it discards on collapse. I must be a very strange and peculiar person for doing that.
-
-
You're right, it only throws away the draft if I collapse.
It only throws away "quote only" if you used the hover "quote reply" button. If you use the standard reply button, whether you have highlighted text it quotes for you or you press the quote post button, it'll hide as if you've started writing a reply.
-
Of course. That's so obvious.
-
And bizarrely consistent for Discourse.
-
Are you sure about that? In vi(m), less, man pages (which I guess use less), the dearly-missed Google Reader, its substitute The Old Reader, Gmail, Google and DDG search results and who knows what else, it's always been j down and k up.
Then I guess it's a case of too many standards. J/K definitely feels backwards to me, though.
-
You're not kidding, are you?
-
-
Yes, abandon No, keep
