After clicking a reply quote the timeline jumps (sometimes days) up to the original and the reader is stranded; "jump to latest" goes to the bottom, not back to where they were.
Scope
On a reply-quote jump, remember the event id that was at the top of the viewport. Show one small chip at the bottom of the timeline — ↓ Back to where you were — only after such a jump; it disappears after ~20 s or as soon as the user scrolls past the remembered position.
Not a setting, nothing rendered in the normal state. Follows the existing "jump to latest" chip styling.
Also applies to thread-panel → main-timeline jumps and search-result jumps (same mechanism).
After clicking a reply quote the timeline jumps (sometimes days) up to the original and the reader is stranded; "jump to latest" goes to the bottom, not back to where they were.
### Scope
- On a reply-quote jump, remember the event id that was at the top of the viewport. Show one small chip at the bottom of the timeline — **↓ Back to where you were** — only after such a jump; it disappears after ~20 s or as soon as the user scrolls past the remembered position.
- Not a setting, nothing rendered in the normal state. Follows the existing "jump to latest" chip styling.
- Also applies to thread-panel → main-timeline jumps and search-result jumps (same mechanism).
Done in 7da91bd8: a reply-quote click (or an eventId route change — thread panel, search, permalink) remembers the message in the middle of the viewport and shows a Primary chip next to Jump to Latest, Back to where you were, which scrolls/navigates back to it; it expires after 20 s or on use, and nothing renders otherwise. Verified headless: reply quote → original 120 messages up + chip; chip → back at the reply, chip gone.
Done in `7da91bd8`: a reply-quote click (or an eventId route change — thread panel, search, permalink) remembers the message in the middle of the viewport and shows a Primary chip next to Jump to Latest, **Back to where you were**, which scrolls/navigates back to it; it expires after 20 s or on use, and nothing renders otherwise. Verified headless: reply quote → original 120 messages up + chip; chip → back at the reply, chip gone.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After clicking a reply quote the timeline jumps (sometimes days) up to the original and the reader is stranded; "jump to latest" goes to the bottom, not back to where they were.
Scope
Done in
7da91bd8: a reply-quote click (or an eventId route change — thread panel, search, permalink) remembers the message in the middle of the viewport and shows a Primary chip next to Jump to Latest, Back to where you were, which scrolls/navigates back to it; it expires after 20 s or on use, and nothing renders otherwise. Verified headless: reply quote → original 120 messages up + chip; chip → back at the reply, chip gone.