[Bug]: Usage Day breakdown columns overlap in narrow windows
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in apps/web by locating the Usage page's Day breakdown table and reproduce the overlap at a 390px-wide viewport with Cost and 30 days selected. Inspect the table's responsive layout and verify that headers and values remain readable, with horizontal scrolling available when needed.
Written by the indexing model from the issue text.
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce the problem.
Area
apps/web
Steps to reproduce
- Have usage activity from Codex, Claude Code, and OpenCode within the selected period.
- Open Usage, select Cost and 30 days, then choose Day under Breakdown.
- Resize the web viewport to 390px wide and scroll to the breakdown table.
Expected behavior
Column headers and values remain readable. A narrow viewport can scroll the table horizontally if needed.
Actual behavior
Provider headers and adjacent dollar amounts overlap. The fixed table reserves 40% for the date and divides the remaining 60% among the provider, total, and token columns.
Impact
Minor bug: daily usage amounts are hard to read in narrow windows.
Version or commit
main @ d15210cd3d
Environment
macOS, T3 Browser panel, web client at a 390 × 700 CSS-pixel viewport. Reproduced with real usage data copied into isolated development state.
Workaround
Widen the viewport. The same table is readable at 640px.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 8h 58m
- Merged PRs (30d)
- 278
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
-
[Bug]: Server git tests sign fixture commits with the developer's key when run from the repo rootOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pingdotgg/t3code#17402 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
check:passed streams:add
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
beta technical-medium ui
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
walletbeat/walletbeat#1625 ·
Maintainers usually reply within 1 day
-
Good First Issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hiero-ledger/hiero-sdk-js#4489 ·
Maintainers usually reply within 1 day
-
[Bug] The clients language filter cannot select the rows the page labels as unknownPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/rocketmq-dashboard#6103 ·
Maintainers usually reply within 4 days
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#18652 ·
Maintainers usually reply within 1 day