Skip to content

Mobile: combine scroll-to-bottom button with working timer #10840

Description

@repparw

On mobile, combine the centered “Working for Xm Ys” pill with the adjacent scroll-to-bottom button, making the whole pill a larger tap target.

This would improve ergonomics, especially for left-handed use.

Activity

  1. repparw commented on Sep 8, 2026

    @repparw
    ContributorAuthor

    file_00000000a50c820ea4126621d23ba4e4.png

    rough concept by gpt (original is not that right aligned but you get it)

  2. juliusmarminge commented on Sep 8, 2026

    @juliusmarminge
    Member

    Thanks for the report — this is a real mobile ergonomics gap, not a missing feature.

    Today: FloatingWorkingControl already draws the centered “Working for…” capsule and the scroll-to-end chevron as two siblings that share a center and slide apart. The timer is intentionally non-interactive (touches pass through to the feed); only the small circle on the right scrolls. That’s awkward for left-handed use. Connection status is a separate case: that capsule is already a reconnect button.

    Not a duplicate of #5434 (closed). That issue asked to add scroll-to-end; #5986 landed it. This issue is about combining tap targets once both chrome are visible.

    Scope: mobile only (apps/mobile/src/features/threads/floating-working-control.tsx, wired from ThreadDetailScreen.tsx). Web keeps “Working for” in the timeline and a separate “Scroll to end” pill.

    Implementation notes

    • Combine only when a non-connection status and showScrollToEnd are both on: one pill (label + chevron) whose press is onScrollToEnd.
    • Leave scroll-only as the existing circle; leave status-only pass-through.
    • Do not steal the connection pill’s reconnect tap.
    • Apply the same layout on iOS glass and the Android/fallback pill.
    • Combined accessibility label: “Scroll to end”.

    The GPT mockup in the first comment didn’t attach; a re-upload is welcome but not required.

    Accepting as a small enhancement.

  3. added
    enhancementRequested improvement or new capability.
    acceptedfeature request accepted
    via-triageFiled through npx t3 triage
    on Sep 8, 2026
  4. juliusmarminge commented on Sep 8, 2026

    @juliusmarminge
    Member

    what iOS is this? This is how it's supposed to look and work:

    ScreenRecording_09-08-2026.15-29-57_1.MP4
  5. repparw commented on Sep 9, 2026

    @repparw
    ContributorAuthor

    sorry, android! just noticed it didn't make it into the body

    edit: the concept's "before" positioning is off, yes, just illustrative Screenshot_20260908_185443_T3 Code.jpg

    still too far right for left thumb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    acceptedfeature request acceptedenhancementRequested improvement or new capability.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions