[Bug]: Android: scroll-to-bottom arrow is shown even when already scrolled to the very bottom
维护者通常 1 天内回复
还没有人认领这个 Issue。
- #12860 来自 @macodev00 —— 已关闭，未合并
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 65/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- mobile
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- Open a thread in the Android client.
- Scroll the chat all the way down, so the view is at the very bottom (latest message fully visible, no more content below).
- 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
- 主要语言
- TypeScript
- 星标
- 24.8k
- 派生
- 6.4k
- 平均合并
- 3 小时 39 分钟
- 30 天内合并 PR
- 301
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pingdotgg/t3code 的其他 Issue
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
pingdotgg/t3code#22819 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
相似的 Issue
-
bug P3 UI/UX
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
StellarState/SS-backend#712 ·
维护者通常 1 天内回复
-
area: backend bug
难度 2/5 1-3 小时 新手友好度 78/100
snapotter-hq/SnapOtter#3473 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
gitroomhq/postiz-app#2304 ·
维护者通常 1 天内回复
-
harlan-agent-ready-to-implement routine:ci-review
难度 2/5 1-3 小时 新手友好度 72/100
harlan-zw/unlighthouse#454 · 2 条评论 ·
维护者通常 1 天内回复