Skip to content

fix(detail): page-level vertical scroll + contain description content (0.22.3)#53

Merged
FelipeCarillo merged 3 commits into
mainfrom
claude/fix-detail-scroll-022-3
Jun 16, 2026
Merged

fix(detail): page-level vertical scroll + contain description content (0.22.3)#53
FelipeCarillo merged 3 commits into
mainfrom
claude/fix-detail-scroll-022-3

Conversation

@FelipeCarillo

Copy link
Copy Markdown
Owner

Problem (reported from browser inspection)

Two issues remained on the focused ticket page after 0.22.2:

  1. No vertical scroll. The container holding the page (.content-body) had overflow: hidden for the detail page and the bounded-height / per-column-scroll scheme never engaged.
  2. Description content escaped its card, forcing a horizontal scrollbar — wide elements (tables, long tokens) leaked outside the description box.

Fix

1. Page-level vertical scroll

Stop pinning the detail page to the viewport height. Removed the .content-body:has(> [data-detail-page]) { overflow: hidden; display:flex } override and the per-column overflow-y: auto, so .content-body keeps its normal overflow-y: auto and the whole page scrolls as one — exactly like every other non-board page (and matching the manual fix found in the inspector). Toolbar, header and grid now stack at natural height.

The right rail (properties/activity) is now position: sticky so it stays in view while a long description scrolls past — preserving the "context always visible" intent of the old per-column design without the fragile height chain. (.detail-sidebar on doc pages already uses sticky.)

2. Contain description content (no horizontal scroll)

  • Long unbreakable tokens (URLs, inline code, paths) wrap via overflow-wrap: break-word on .detail-section-body instead of widening the column.
  • Wide tables scroll inside their own box (display: block; overflow-x: auto) rather than pushing the layout wider.
  • (Code blocks already had overflow-x: auto; images already capped at max-width: 100%.)

Net: nothing leaks past the description card, and no page-level horizontal scrollbar is needed.

Files

  • detail.css — page-scroll layout + sticky rail
  • markdown.css — content containment (wrap + responsive tables)

Release

Bumps to 0.22.3 + CHANGELOG. Merging to main triggers the release workflow (PyPI + GitHub release).

Note: still no browser in this environment to render it, so this is reasoned from the layout chain + the inspector findings you reported (content-body overflow:hidden blocking vertical scroll; content leaking out of the description). Please give it a quick visual check on a ticket with a long description / a wide table before relying on it.


Generated by Claude Code

claude added 3 commits June 16, 2026 15:21
The viewport-pinned layout with independently scrolling grid columns kept
breaking (no vertical scroll, stray horizontal scrollbar). Switch the ticket
detail page to plain page-level scrolling inside .content-body — drop the
'overflow:hidden' bounded-height override and the per-column overflow-y:auto;
toolbar/header/grid stack at natural height and scroll as one. The right rail
is now position:sticky so properties/activity stay in view.

Contain rendered description content so nothing escapes the card and no
horizontal scroll is needed: long unbreakable tokens wrap (overflow-wrap),
wide tables scroll inside their own box (display:block; overflow-x:auto).
Code blocks and images were already contained.
The TestDetailPageScrollContainment suite pinned the old viewport-height /
independent-column-scroll design (content-body overflow:hidden, overflow-y:auto
on the columns) — the very scheme that kept breaking. Rewrite it to assert the
new invariants: page scrolls via .content-body (no bounded-height override),
columns no longer self-scroll, the rail is sticky, and description content is
contained (overflow-wrap + responsive tables).
@FelipeCarillo FelipeCarillo merged commit aa83a9c into main Jun 16, 2026
11 checks passed
@FelipeCarillo FelipeCarillo deleted the claude/fix-detail-scroll-022-3 branch June 16, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants