Skip to content

fix(ux): Reset timeline selection and scroll on refresh#230

Merged
ainergiz merged 3 commits intomainfrom
claude/reset-timeline-refresh-bp92C
Jan 13, 2026
Merged

fix(ux): Reset timeline selection and scroll on refresh#230
ainergiz merged 3 commits intomainfrom
claude/reset-timeline-refresh-bp92C

Conversation

@ainergiz
Copy link
Owner

When pressing 'r' to refresh the timeline, automatically reset selection
to index 0 and scroll to the top. This provides clear visual feedback
that the refresh completed and shows the user the newest content.

Detects refresh by tracking when the first post ID changes, indicating
the posts array was replaced with new content. This also applies to
tab switches in TimelineScreen, BookmarksScreen, and ProfileScreen.

claude and others added 3 commits January 6, 2026 18:06
When pressing 'r' to refresh the timeline, automatically reset selection
to index 0 and scroll to the top. This provides clear visual feedback
that the refresh completed and shows the user the newest content.

Detects refresh by tracking when the first post ID changes, indicating
the posts array was replaced with new content. This also applies to
tab switches in TimelineScreen, BookmarksScreen, and ProfileScreen.
…hange

The previous approach only reset to top when the first post ID changed,
which didn't work if no new tweets arrived. Now each screen tracks a
refreshKey counter that increments on 'r' press, and PostList resets
when this key changes - regardless of whether content changed.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…-refresh-bp92C

# Conflicts:
#	src/screens/ProfileScreen.tsx
@ainergiz ainergiz merged commit ea85bde into main Jan 13, 2026
3 of 4 checks passed
@ainergiz ainergiz deleted the claude/reset-timeline-refresh-bp92C branch January 13, 2026 00:21
@ainergiz ainergiz mentioned this pull request Jan 17, 2026
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants