[Bug]: Android pending-answers card's Submit button is hidden behind the 3-button navigation bar (Samsung One UI)

未关闭
#39,263 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
android, react-native, typescript
领域
frontend, mobile

调研方向

Start in the apps/mobile thread screen and trace how the pending-answers card is laid out alongside Android system insets. Reproduce on Android with 3-button navigation, then compare the card and composer behavior. Done when the Submit button remains visible and tappable above the navigation bar; check the related thread-screen issue #19345 for context.

由索引模型根据 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
  1. On a Samsung Galaxy S21 Ultra (One UI 7.x, 3-button navigation), open the T3 Code Android app (Google Play build).
  2. Open a thread where the agent asks a question, so the "USER INPUT NEEDED · Fill in the pending answers" card is shown.
  3. Scroll to the bottom of the card, past the options and the "Or type a custom answer" field.
Expected behavior

The card's Submit button sits above the Android navigation bar and can be seen and tapped.

Actual behavior

The pending-answers card runs past the bottom of the visible area. Its Submit button ends up in the system navigation-bar area, level with or under the 3-button navigation, so it is hidden behind the system buttons and cut off in screenshots. The bottom inset does not seem to be applied below this card.

The composer's send button may be affected the same way (it was first reported as sitting in line with the system buttons), but the question card's Submit button is the clear case.

Possibly related: #19345 (thread screen pushed below the nav bar after starting a new chat), closed as fixed. This is a different screen state, so it may be a separate path or a regression.

Impact

Minor bug or occasional failure

Version or commit

2.3.0 (Google Play)

Environment

Samsung Galaxy S21 Ultra, One UI 7.x (exact version unknown), 3-button navigation, T3 Code 2.3.0 (Google Play).

Logs or stack traces

No response

Screenshots, recordings, or supporting files

Pending-answers card running off the bottom of the screen

Cropped to the card. The screenshot ends at the "Or type a custom answer" field: the card continues past the bottom edge, and the Submit button below it is hidden in the navigation-bar area, so it does not appear in the capture.

Workaround

No response

主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
4 小时 29 分钟
30 天内合并 PR
488

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。