OK so I noticed that when you use certain tags that are used to sort the images on E621 (order:score) is an example of one of the tags that restrict certain keyboard shortcuts.
I was wondering why that happens and if there is a way to fix it

sirderpington_th_3rd said:
OK so I noticed that when you use certain tags that are used to sort the images on E621 (order:score) is an example of one of the tags that restrict certain keyboard shortcuts.
I was wondering why that happens and if there is a way to fix it

Yeah I just noticed this as well, quite annoying and it doesn't seem like anyone else has noticed it; have you found a solutions?

if you're talking about the A and D shortcuts (previous and next), it's because sort orders other than post ID are subject to change

consider this scenario:
• you're sorting by score ascending and viewing post X which has score 0,
• you press D and it takes you to post Y with score 2,
• while you're viewing post Y, post X gets a few upvotes and now has score 5,
• you press D and you get served post X again, since X has now moved up in the score-ordered sequence.

The quick navigation is done server side, and it has to be able to quickly find the next or previous post without knowing anything other than the post id you're currently on. When you're sorting posts, it doesn't have enough information to find where you were and take you forwards or backwards. When you're sorting by post id, which is the default, it can very quickly move between posts without having to locate where you are inside a search.

There is no easy fix to this without making the post to post navigation happen in javascript so that it doesn't have to happen on the server side. It's too expensive to complete on the server side.