[Bug]: Wrapped PR titles lose bottom padding in the thread details panel
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
- react, typescript
- Domain
- frontend
Research direction
Start in the apps/web area and trace the PR title row and hover styles in the thread details panel, focusing on how vertical padding behaves when a title wraps. Compare a two-line title with a short single-line title at the panel width. Done when wrapped titles have balanced top and bottom clearance while single-line spacing remains unchanged.
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
- Open a thread with a linked, open pull request that has a visible Merge action in the thread details panel.
- Use a PR title long enough to wrap to two lines at the current panel width. For example:
fix(web): preserve the selected thread when switching projects. - Hover the PR title.
- Observe the space above the first line and below the second line.
- Compare with a short, single-line title.
Expected behavior
Wrapped PR titles should retain balanced vertical spacing inside their hover background, with adequate breathing room below the second line.
Actual behavior
The wrapped title has noticeably more space above the text than below it. The second line sits close to the bottom edge of the hover background.
Below I included 6 screenshots that I personally tried to reproduce.
before refers to 058eea9246ff, the parent commit before #36528. After refers to 0516493a914c, the commit that landed #36528. Main refers to 2a411317d9b7, the origin/main revision tested.
I used short PR titles that fit in one line and longer titles that wraps.
before:
after:
main:
Measurements in CSS px, using the same wrapped title and capture settings.
Clearance is measured from the text line box to the control's border box.
Before #36528: 058eea9246ff
Top clearance: 7.75
Bottom clearance: 7.75
After #36528: 0516493a914c
Top clearance: 7.75
Bottom clearance: 1
Main: 2a411317d9b7
Top clearance: 7.75
Bottom clearance: 1
Single-line control: bottom clearance remains 8 px in all three revisions.
I suggest maintainer(s) or their agents try to reproduce again in case I am wrong.
Impact
Cosmetic issue
Version or commit
Observed on 0.1.11-nightly.20261119.4928; also reproduced at main commit 2a411317d9b7341547e5acb3e9bceb7e6195c5a2. Padding regression seemingly introduced by 0516493a914c193f548b6201463ba6d5f5ad9f70.
Environment
macOS 27.0.0 arm64, T3 Code Desktop with a local server. Comparison screenshots use isolated Chrome fixtures rendering the actual PR-row component and styles with mocked PR data, a 280 px panel, macOS system font, 18 px interface size, and DPR 2. Font and size are capture settings, not prerequisites for the report.
Logs or stack traces
Screenshots, recordings, or supporting files
before-single.png
after-single.png
before-double.png
after-double.png
main-single.png
main-double.png
Workaround
This is cosmetic issue and does not affect normal usage.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 4h 46m
- Merged PRs (30d)
- 488
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 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
[Bug]: Add provider can create a built-in driver's default instance, which has no delete actionPossibly taken @nateEc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#38462 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day
-
Progress indicated by console logs is off by onePossibly taken @marceliwac claimed this today. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/aws-cdk-examples#1336 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#4999 · 1 comment ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
db-ux-design-system/core-web#8856 ·
Maintainers usually reply within 1 day