Skip to content

Fix the phone menu, sticky header, dropdown widths and number headers - #56

Merged
evangress merged 5 commits into
mainfrom
fix/demo-findings
Nov 14, 2026
Merged

evangress merged 5 commits into
mainfrom
fix/demo-findings

Conversation

@evangress

Copy link
Copy Markdown
Collaborator

Four problems found while building the demo pages, each reproduced with Playwright first and covered by a test that failed before the fix.

  • Phone menu covered whatever sat above the header. The panel opened at a fixed 4.5rem; with a banner and family bar above, the ☰ button was at y=183 and the panel at y=72. Where anchor positioning is supported, the panel now opens right under its button (y=233), sticky or scrolled. Elsewhere it keeps today's placement.
  • Sticky header hid headings you jump to. The bar's padding is now --spacing-sm (a two-row phone bar went from 116px to 84px). scroll-padding-top is calc(var(--tag-header-height, 4rem) + 1rem), with 6.5rem on phones. TagAction (kovirlabs/tagaction, same branch name) sets --tag-header-height to the measured height, so even a three-row bar is exact; without it the CSS default covers one- and two-row bars.
  • Dropdowns too narrow. The user menu and header <details> lists are width: max-content, capped to fit a phone. Where anchor-scope is supported the dropdown anchors to its summary and flips to stay on screen (one ran 29px off a 360px screen before).
  • Number column headers without TagAction. A header cell over a column of <data> values now lines up with them, for columns 1–8 of a table with one header row and no colspan in the first rows. An align attribute or page CSS still wins; the docs say to use align="right" beyond that.

Docs: README, llms.txt, llms/*.md and ai/ updated. Size: 12,485 → 12,820 bytes gzipped (budget 15,360). Tests: 530 passed locally in Chromium and WebKit (was 522).

Merge after #55 (the demo page). Both add an ## Unreleased CHANGELOG heading, so I'll resolve that conflict once #55 is in. After release, the demo page's own phone scroll-padding-top workaround can go.

🤖 Generated with Claude Code

evangress and others added 5 commits November 13, 2026 20:48
On phones the popover panel opened at a fixed 4.5rem from the top of the
window, so a banner or family bar above the header put the panel over it
and over the button that opened it (measured at 360px: button at y=183,
panel at y=72). Where anchor positioning is supported the panel now uses
the popover's implicit anchor (position-area: block-end span-all), so it
opens right under the button, sticky or scrolled; elsewhere it keeps the
4.5rem placement.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
header[data-layout="sticky"] kept a plain header's 1.5rem block padding,
so one row was 75-88px against a fixed 5rem (80px) scroll-padding-top,
and on a phone a bar whose links wrap to a second row was 116px, so a
heading reached by a #fragment landed under it (measured at 360px:
heading at y=112 under a 116px bar).

The sticky bar now has --spacing-sm block padding (one row 43-58px, two
rows on a phone 84px). The scroll padding is calc(var(--tag-header-height,
4rem) + 1rem): 5rem as before on wide screens, 7.5rem at 48rem and
narrower, and exactly the bar's height plus 1rem when --tag-header-height
is set (TagAction will measure it).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A user menu popover was squeezed into the anchor area beside its button
(83px wide at 360px), so "Sign out" wrapped; a header <details>
dropdown was a fixed 12rem, so "Tabs, copy, and theme" wrapped, and at
360px one in the middle of the bar ran 29px past the right edge.

Both are now width: max-content, capped at min(100vw - 2 * gutter,
24rem). The user menu's max-width is viewport-based, so a wide menu
overflows the area and the existing flip fallbacks move it. The dropdown,
where anchor positioning and anchor-scope are supported, anchors to its
summary and flips (flip-inline, then centered) to stay on screen.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A <data> value alone in a cell was right-aligned, but the <th> above it
stayed left-aligned unless TagAction marked it data-tag="num". CSS
can't select a column, so a header cell is matched to the first body
row's cell in the same place with :has() and :nth-child(), for columns
1-8 of a table with one header row. A colspan in the header row or the
first body row leaves the headers alone, and an align attribute wins.

The scoped and Shadow DOM builds' leftover check now looks for
"body >" as a word, so "tbody > tr" doesn't trip it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@evangress
evangress merged commit ec3de46 into main Nov 14, 2026
2 checks passed
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.

1 participant