Skip to content

fix(timeline): restore isReady recovery on failed jump-to-event#812

Draft
Just-Insane wants to merge 2 commits into
SableClient:devfrom
Just-Insane:fix/timeline-jump-scroll
Draft

fix(timeline): restore isReady recovery on failed jump-to-event#812
Just-Insane wants to merge 2 commits into
SableClient:devfrom
Just-Insane:fix/timeline-jump-scroll

Conversation

@Just-Insane
Copy link
Copy Markdown
Contributor

Description

When navigating to an event via a notification, useTimelineActions calls focusItem which sets isReady = false to hide the timeline during the jump animation. If the jump fails (event not in timeline, Matrix SDK error, etc.) isReady was never restored to true, leaving the timeline permanently blank for that room session.

Adds a finally clause that always calls setIsReady(true) after the jump attempt, regardless of success or failure.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings

AI disclosure:

  • Partially AI assisted (clarify which code was AI assisted and briefly explain what it does).

The AI identified the missing finally recovery clause in the jump-to-event flow. The fix is a single finally { setIsReady(true) } block — I understand what it does and have verified it doesn't interfere with the success path (which also calls setIsReady(true)).

…nt jumps

Add a short-lived jump scroll block (~350 ms) after scrollToIndex calls
so intermediate scroll events from the animation don't prematurely flip
atBottom and show the "Jump to Latest" button when the user is already
at the intended location.
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.

1 participant