[Bug]: Settled list toggle is obscured by bottom navigation on unfolded iPhone Duo in portrait
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
- mobile
Research direction
Start in the apps/mobile area and trace the sidebar thread list and floating bottom navigation layout. Reproduce the reported overlap on an unfolded iPhone Duo in portrait, then inspect the relevant layout and safe-area handling. Done when the Settled toggle remains fully visible and reachable without overlapping the navigation bar.
Written by the indexing model from the issue text.
Description
Area
apps/mobile
What happened
On my iPhone Duo, unfolded and held vertically (portrait), the Settled list toggle at the bottom left appears behind the floating bottom navigation bar in the sidebar. The toggle is partly obscured.
Steps to reproduce
- Open T3 Code on an iPhone Duo with the device unfolded and in portrait orientation.
- View the sidebar/thread list with the Settled toggle visible at the bottom left.
- Observe the overlap between the Settled toggle and the floating bottom navigation bar.
Expected behavior
The Settled toggle should remain fully visible and reachable without overlapping the navigation bar.
Actual behavior
The navigation bar covers part of the Settled toggle.
Environment
- Device: iPhone Duo, unfolded
- Orientation: portrait / vertical
- iOS: 27.2
- T3 Code: 2.2.0
This is a user-observed layout issue, not an independently reproduced test. Tap behavior, frequency, and recovery steps have not been confirmed.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 14h 40m
- Merged PRs (30d)
- 193
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pingdotgg/t3code#27767 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: Dragging a sidebar thread from the lower part of the list auto-scrolls the sidebar to the bottomPossibly taken @juliusmarminge claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pingdotgg/t3code#27445 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#27146 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
backend bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
geolens-io/geolens#3568 ·
Maintainers usually reply within 1 day
-
area:docs documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
API: `tsc.exe` opens a visible console window on Windows when the parent process has no consoleOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/TypeScript#65083 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug p2 platform:web triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day