[Bug]: Wrapped PR titles lose bottom padding in the thread details panel

未关闭 适合新手
#39,144 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
72/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
react, typescript
领域
frontend

调研方向

从 apps/web 区域开始,追踪线程详情面板中的 PR 标题行和悬停样式,重点查看标题换行时垂直内边距的表现。在面板宽度下,对比两行标题和简短的单行标题。完成标准是:换行标题上下留白均衡,同时单行标题的间距保持不变。

由索引模型根据 Issue 内容生成。

描述

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/web

Steps to reproduce
  1. Open a thread with a linked, open pull request that has a visible Merge action in the thread details panel.
  2. 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.
  3. Hover the PR title.
  4. Observe the space above the first line and below the second line.
  5. 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:
before-single

before-double

after:

after-single after-double

main:

main-single main-double

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.

主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
4 小时 46 分钟
30 天内合并 PR
488

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。