[Bug]: PR link chips in an expanded Markdown table break mid-number (#36 / 3)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, react, typescript
- Domain
- frontend
Research direction
Start in apps/web/src/index.css and inspect the expanded-table fit rules under the @container chat-lane (min-width: 36rem) condition, then trace the PR link chip styling if needed. Reproduce with the provided narrow PR column and long prose in an expanded Markdown table. Done when the chip stays on one line and its column is wide enough to display it.
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 or investigate the problem.
Area
apps/web
Steps to reproduce
-
In a thread with a chat lane at least 36rem wide (the desktop window was about 2000px wide, right panel open), get an assistant reply containing a Markdown table. Put GitHub pull request links in a narrow first column and long prose in the other columns, for example:
| PR | What it does | Review | | --- | --- | --- | | [#363](https://github.com/owner/repo/pull/363) | A long sentence of prose that takes up most of the row width and wraps over several lines in the expanded table. | Another long sentence of prose that also wraps over several lines in the expanded table. | | [#364](https://github.com/owner/repo/pull/364) | A long sentence of prose that takes up most of the row width and wraps over several lines in the expanded table. | Another long sentence of prose that also wraps over several lines in the expanded table. | -
Leave the table in its expanded state (the "Collapse table cells" button is showing).
Expected behavior
The PR link chip (GitHub icon plus #363) stays on one line, and the column is at least as wide as the chip.
Actual behavior
The first column gets squeezed and the chip's number breaks in the middle: the icon and #36 on one line, 3 alone on the next, the same for #364. The prose columns get most of the width.
This looks like it comes from the expanded-table fit rules added in #20878 (apps/web/src/index.css, @container chat-lane (min-width: 36rem)): the table gets min-width: 0 and cells get overflow-wrap: break-word, and nothing keeps the PR link chip from breaking. Those rules are unchanged on main as of 66ee628e08.
Impact
Cosmetic issue
Version or commit
0.1.2-nightly.20261022.3526 (f054d1b80187). No newer nightly up to 0.1.3-nightly.20261023.3579 changes this.
Environment
macOS, T3 Code (Nightly) desktop app connected to a remote T3 server on Debian Linux (kernel 6.12). Provider Claude, model Opus 5.5.
Logs or stack traces
No response
Screenshots, recordings, or supporting files
I can add a cropped screenshot if useful.
Workaround
Probably collapsing the table with "Collapse table cells", which keeps natural column widths and scrolls sideways. Not confirmed.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 4h 35m
- Merged PRs (30d)
- 174
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 needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[Bug]: Forgejo skipped status keeps watch_pull_request pending when no required-check policy is setOpen
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
MCP endpoint matches the Authorization scheme case-sensitively and logs the same reason for "absent" and "wrong scheme" (ChatGPT connector gets missing_bearer_token)Possibly taken @shethshlok claimed this 1 day ago. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
bug hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
libredb/libredb-studio#1941 ·
Maintainers usually reply within 1 day
-
chore other
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
alastair-smith/card-games#308 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
paperclipai/paperclip#17379 ·
Maintainers usually reply within 1 day
-
[good first issue, hacktoberfest] 🏯 Hacktoberfest Task - Add new Anime Quote 626 (good-first-issue)Opencommunity first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
lingdojo/kana-dojo#33040 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug mobile ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day