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

Offen
#39,263 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
68/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
android, react-native, typescript
Bereich
frontend, mobile

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 29 Min.
Gemergte PRs (30 T.)
488

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.