Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Android: scroll-to-bottom arrow is shown even when already scrolled to the very bottom

Open
#12,754 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #12860 by @macodev00 — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
mobile

Research direction

Start in apps/mobile and trace the Android thread view's scroll-to-bottom arrow visibility behavior, including the streamed-output auto-scrolling path. Reproduce the issue with a thread at the latest message, then verify the arrow is hidden at the bottom and appears only after scrolling upward, including after returning to the bottom.

Written by the indexing model from the issue text.

Description

accepted bug via-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/mobile

Steps to reproduce
  1. Open a thread in the Android client.
  2. Scroll the chat all the way down, so the view is at the very bottom (latest message fully visible, no more content below).
  3. Observe the floating scroll-to-bottom arrow/pill.
Expected behavior

The scroll-to-bottom arrow should hide whenever the list is already scrolled fully to the bottom. It should only appear when the user has scrolled up away from the latest content, and disappear again as soon as they reach the bottom.

Actual behavior

The arrow is still shown even when the list is already scrolled as far down as possible. It sits over the newest messages and invites a tap that has nowhere to go. It also seems to reappear while streamed output is auto-scrolling, when the view is effectively pinned to the bottom.

Possibly related: #2119 (scroll-to-bottom pill visibility after navigating to a new thread), which suggests the pill's visibility logic has had tracking issues before.

Impact

Cosmetic issue

Environment
  • Device: Xiaomi 15 on HyperOS 4 beta 3 (CN ROM)
  • Platform: Android client (current build as of 2026-09-20)

🤖 GLM 5.3 Flash on behalf of iliasgws

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
13h 9m
Merged PRs (30d)
271

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.