[Bug]: Toolbar covers up chat text input field

Open Beginner friendly
  • Is something wrong?
#35,201 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
react-native, typescript
Domain
frontend, mobile

Research direction

Start in the mobile app area and trace the chat input and the toolbar layout on iPadOS. Reproduce the issue on an iPad running iPadOS 18.6.2 by opening a thread and typing in the chat field. Done means the toolbar no longer obscures the text being entered; verify that the input remains visible while typing.

Written by the indexing model from the issue text.

Description

bug needs-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 T3 Code on iPad OS 18.6.2
  2. Select any thread in the sidebar to start or continue a chat
Expected behavior
  1. Type text in the chat text field and see what you're typing.
Actual behavior
  1. The toolbar containing the chat, PR, usage, and settings icons obscures about 30% of the text chat field, so you can't see what you're typing.
Impact

Major degradation or frequent failure

Version or commit

2.30

Environment

iPad OS 18.6.2

Logs or stack traces
Screenshots, recordings, or supporting files

ipad_screenshot.jpeg

Workaround

You can enter a few line breaks in the chat text box and then arrow the cursor up and begin typing on top of those line breaks to see what you're typing - but only if you have a keyboard connected to the iPad. Without a keyboard I'm not sure how you easily work around this. While thinking of workarounds I also noted there's no audio input to the chat box, which seems like a notable feature omission.

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
4h 16m
Merged PRs (30d)
352

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.