Naiyuan Qing 4c7fefd143 fix(editor): cap issue mention chip at container width, no clickable gap (#4295) ...

#4288 swapped the chip cap from a fixed `max-w-72` to `max-w-[min(18rem,100%)]`.
A percentage max-width on a flex item is dropped while its flex-container wrapper
(`<a class="inline-flex">`) computes its own max-content size, so the wrapper
ballooned to the untruncated title width while the chip truncated to the cap —
leaving an empty, clickable strip after the visible chip.

Fix it as standard atomic-inline behavior instead of a fixed magic cap:
- IssueChip caps at `max-w-full` with the title truncating to an ellipsis, so it
  wraps to the next line as a unit and only truncates once a whole line can't
  hold it.
- Drop `inline-flex` from the editor NodeView `<a>` (issue + project) and the
  markdown AppLink so the chip's only wrapper is a plain inline box with a
  definite (line-based) percentage basis — no second flex container to balloon.

ProjectChip uses a definite `max-w-72`, so it never hit the gap; left as-is.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-18 14:11:07 +08:00

..

actions

fix(clipboard): support copy over http:// via execCommand fallback (#3810)

2026-06-05 14:55:23 +08:00

components

fix(editor): cap issue mention chip at container width, no clickable gap (#4295)

2026-06-18 14:11:07 +08:00

hooks

feat(chat): workspace-scoped attachment binding + fire-and-forget send (#4249)

2026-06-18 09:40:38 +08:00

utils

chore: react-doctor cleanup — button types, useContext→use(), toSorted, error fixes (#3350)

2026-05-27 14:57:07 +08:00