npub1w85l93z2dyetvaev42kvmgv3r5qsgc7rutrvgpqshqefj4sydqqskwstfmandTom Brow bde10f65cf fix(mobile): keep the unread jump after a deep boundary give-up ...

The unread-boundary effect bailed out entirely once it gave up paging
toward the target, so a channel whose oldest unread sat further back
than the four-fetch cap never offered the jump control again for that
visit, even after the user scrolled the target into view themselves.

Scope the give-up flag to fetching, which is what it is for, and let
candidate resolution keep running. Direction of the bug was fail-closed
(a missing control, never a wrong jump), so this only restores a
control that PR #4239's predecessor head offered.

Co-authored-by: Tom Brow <tomb@block.xyz>
Signed-off-by: Tom Brow <tomb@block.xyz>

2026-08-03 17:58:38 -07:00

..

features

fix(mobile): keep the unread jump after a deep boundary give-up

2026-08-03 17:58:38 -07:00

helpers

Rename mobile app to Buzz (#955)

2026-06-10 13:38:11 -07:00

shared

fix(mobile): recover stale relay sessions (#4372)

2026-08-03 12:28:50 -07:00

widget_test.dart

Rename mobile app to Buzz (#955)

2026-06-10 13:38:11 -07:00