Repository navigation
k at page top lands on the last story of the previous page - #33
Merged
Merged
Conversation
Going back with k used to land on the previous page's first story because position memory is per-feed. j/k-triggered page switches now carry an explicit landing target (Start for j, End for k) that set_stories_for applies when the new page loads; manual n/p keep the existing position-restore behavior. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
Shaance
force-pushed
the
feat/jk-land-at-page-edge
branch
from
November 5, 2026 16:34
e5b8433 to
a963c8b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
j/k-triggered page switches now carry an explicit landing target: j past the last story lands on the next page's first story, k at the top lands on the previous page's last story (previously both landed on the first story, since position memory is per-feed). Manual n/p keep the existing position-restore behavior. Based on fix/jk-no-stack-during-fetch (#32).