Repository navigation
Land the stacked branches on main (#45–#50), TagBrush.css 2.0.0 unreleased - #51
Merged
Merged
Conversation
Roadmap chunk 23. An evaluation against modern-web practice found that TagBrush.css barely responds to the user, and that some HTML says what the author means but was styled like plain elements. - Dialogs and popovers fade and grow in, and fade out where display can animate (@starting-style, transition-behavior, overlay); backdrops too. - Pages of the same site cross-fade (@view-transition), unless the reader prefers reduced motion. Opt out with navigation: none (checked in Chromium on a local server). - A card whose heading holds its only link is clickable all over, with hover and focus on the card. - A <details> in the header nav is a dropdown menu, no JavaScript; it opens in place inside the phone menu panel. - Wide tables and code blocks show a shadow at an edge with more to scroll to (scroll-driven; Chromium and Safari 26). - Header nav links are at least 44px tall on touch screens. - Links to PDF, DOC, XLS, CSV and ZIP files say so; download links get an arrow. Buttons, nav links and image links are left alone. Also in ROADMAP.md: the later items, what isn't planned (scroll reveals, parallax, sticky header by default), and an open question on moving the default look away from what AI-built sites cluster around. 10.1 KB gzipped (ceiling 15 KB); llms.txt 3,748 tokens (cap 4,000). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Choice cards: a radio or checkbox label with a <small> description is a card, outlined when chosen; a fieldset of them is a row. - Pull quote (figure > blockquote + figcaption) and round avatars for an <img> in a figcaption, an article footer, or an <address>. - A <data> value alone in a cell aligns right in tabular figures; table rows highlight under the pointer on devices that hover. - An <iframe> without a height fills the width at 16:9. - With a mouse, selects open a themed picker where appearance: base-select is supported. The arrow is absolutely positioned so a site's own display on selects can't wrap it (the demo page's inline select did). - :user-valid turns fields with a rule green; fields without one stay neutral. - scrollbar-color from the theme; prefers-contrast: more darkens borders and makes muted text full contrast. Not done, with reasons in ROADMAP.md: a sticky table header (the figure only scrolls sideways) and :autofill (browsers' own tint overrides the field background). The sale price needed only a guide line; <s> was already muted. 10.6 KB gzipped; llms.txt 3,910 of 4,000 tokens. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Roadmap chunk 24. llms.txt is now an index every agent reads: the rules and every pattern in one line, grouped by what you're building, each group linking to a detail file in llms/ (pages, apps, forms, content, chat) with full examples and what each pattern leaves alone. The build writes llms-full.txt (everything in one file), the Claude Code skill with the detail files as references, one Cursor rule per topic, and a full AGENTS.md. CI: the contract tests cover every guide file; every pattern named in a detail file must be named in the index; the index is capped at 4,000 tokens (3,038, down from 3,910) and the full guide at 20,000 (8,311). Evaluation round 3: the landing and sign-up requests, each written by fresh agents with the old guide, the index alone, and the full guide. All six pages are clean with every guide, and the index alone matched the full guide; the requests are too easy to separate them. Findings, follow-ups, and the pages are in evals/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Interaction, and styling from what the HTML means
Chunk 23, later items: choice cards, pull quotes, data, embeds, pickers
Split the agent guide into an index and detail files
TagAction now switches role="tabpanel" panels and adds the arrow keys (kovirlabs/tagaction#1); this styles the tabs themselves. Without TagAction every panel shows. The guide's apps detail file and index list the pattern. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…(D2) <del>−0.4%</del> in a stat tile was struck through on a red highlight, so a drop read as a deleted value. In a <dl> of <div>s, <ins> and <del> are now green and red text (mixed with the text color for 4.5:1) after ▲ and ▼, with no line and no background. Elsewhere they are unchanged (tested). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The grid's auto-fit tracks never collapsed, because the copyright line spans them all, so two nav columns bunched at the start and left half the row empty. The footer is now a wrapping flex row: a leading paragraph takes the free space (up to 24rem), the navs are 10rem columns at the end, and a last paragraph spans the width. Columns wrap on phones (tested at 360px). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A button that opens something now says so: a chevron after its label, pointing up while aria-expanded="true". Covers TagAction's dropdown buttons. Buttons without the attribute, links styled as buttons, and popovertarget buttons are unchanged (tested). Demo snapshots updated for the new example. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A solid toggle takes its hover color and an inset shadow; an outline or secondary one fills with a tint of the primary color and full-contrast text. TagAction's Show/Hide and theme buttons gain a visible state. aria-pressed="false" is unchanged. Contrast fixture covers all three. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
<button data-tone="error">Delete</button> is solid red, and with class="outline" red-bordered; every tone and style="--tone: …" works. The fill is the tone darkened to OKLCH lightness 0.5 at most, so white text passes 4.5:1 in both schemes (contrast fixture covers each tone, solid and outline). The demo's confirm dialog uses it. The automatic- contrast tests read a demo button by id now that the dialog's confirm button is red. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
In a form that also has optional fields, the label of a required field (a <label> right before it, or one wrapping it) ends in " *" in the error color, with empty alt text since the field already says it's required. A form where every field is required (a sign-in) gets none; buttons and hidden inputs don't count as optional fields. Tested both. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A <p>, <div>, <section> or <aside> with role="status" is an info-tinted banner and with role="alert" a red one; data-tone recolors either. Fill only, no border. Left alone (tested): empty live regions waiting for a message, inline status spans, and regions TagAction adds (data-tag). Contrast fixture covers all three tones. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The <details> marker is a chevron instead of the browser's triangle: at the start of the summary (turning down when open, mirrored in RTL), or at the end in an accordion (neighboring details or a name), turning up. The header-nav dropdown keeps its own chevron (tested). Opening eases the height with interpolate-size and ::details-content, behind @supports selector(::details-content), following the modern-web-guidance animate-to-intrinsic-sizes guide: interpolate-size is opted into on details only, overflow is clipped with a focus-ring margin, and browsers without it (WebKit here; checked with CSS.supports in the test) open at once, as does prefers-reduced-motion. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
:root:has(dialog:modal) { overflow: hidden }, with scrollbar-gutter:
stable on the root so the page doesn't shift sideways when its scrollbar
goes away. Non-modal dialogs (show()) leave the page alone (tested, with
a wheel scroll that must not move the page). In the page layout section,
so the scoped and Shadow DOM builds leave it out. The CHANGELOG notes the
gutter on short pages with classic scrollbars and how to undo it.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ow-up) Found in the screenshots: TagAction's Show/Hide row puts a role="group" between the password label and its field, so the sign-up template's required password had no asterisk. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Opt-in, as decided: the page header sticks to the top on the page background; the root gets scroll-padding-top: 5rem so jumped-to headings and focused fields land below it (WCAG 2.4.11); once stuck, a soft shadow (a ::after gradient) fades in through a named scroll-state container query. Following the modern-web-guidance state-aware-sticky-headers guide: the container is named, only a pseudo-element's opacity changes (no layout shift, so no overflow-anchor), and without scroll-state support (WebKit here, checked with CSS.supports in the test) the bar still sticks with its hairline. Headers without the attribute are unchanged (tested). In the page layout section, so scoped and Shadow DOM builds leave it out. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A link in running text with target="_blank" ends in " ↗", with alt text "(opens in a new tab)". Buttons, nav links, heading links (cards), image links, and document or download links (which have their own label) are left alone (tested). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Tabs: a role="tablist" row with the selected tab underlined
A popover holding a nav or list (a user menu) is anchored to the button that opened it (implicit anchor from popovertarget): position-area block-end span-inline-start, with flip-inline / flip-block fallbacks. Following the modern-web-guidance viewport-aware-dropdowns guide without a polyfill: inset: auto and margin are set only inside @supports (position-area: block-end), so other browsers keep the centered popover. Plain popovers and the phone menu are unchanged (tested: left, right edge, bottom-edge flip, centered note; Chromium and WebKit both support it here). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
tbody tr:has(> :first-child > input[type=checkbox]:checked) gets a 10% primary tint (also with the checkbox inside a label). False matches left alone (tested): a toggle switch in the row, a checkbox in a later cell. Contrast fixture covers text on a selected row. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
In @media print: nav, search bars, buttons (except TagAction's sort buttons, which hold the header text), and tab rows are display: none; articles, stat tiles, steps, details, asides, and banners avoid page breaks inside; ::details-content of closed <details> is shown (where supported), so a printed FAQ has its answers even without TagAction. Tested with emulated print media; links styled as buttons still print. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A field just under the sticky header, focused the way form validation does, scrolls out from under it thanks to scroll-padding-top (Chromium). Skipped in WebKit, where focus() scrolling measurably stops about 5px short of scroll-padding-top; TagAction now scrolls the first invalid field to the middle itself, tested there in both engines. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
CSS only, as the list asks: [popover="hint"] gets the text color as its background, small type, and a light shadow; inside @supports (position-area: block-start) it sits above its implicit interestfor anchor with flip fallbacks. Following the modern-web-guidance interest-triggered-tooltips guide's no-polyfill path; the guide's ARIA script is out of scope (no tooltip JS in the family), so the docs have authors write role="tooltip" and aria-describedby, and say to keep needed information out of tooltips. A link with interestfor gets a dotted underline as the visual cue. Tested: looks in both engines; hover opens it above the button in Chromium (interestfor), skipped in WebKit. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
input[type=search] inside <search> or form[role=search] gets a magnifier drawn with a radial and a linear gradient in --color-text-muted (so it follows the theme and dark mode, which an SVG data URL can't), with room for it at the start, mirrored in RTL. Search fields outside a search bar are unchanged (tested); checked visually at 2x. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Under 30rem, dialog:where(:modal) is full width, docked to the bottom edge (margin: auto 0 0), at most 85dvh tall, with only a top border and rounded top corners. It slides up (translate from 100%, @starting-style) instead of growing; reduced motion makes it instant as before. Wider screens stay centered (tested both). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Checked first (screenshot at 360px): the dashboard's sidebar stacks its whole link list between the top bar and the page. New page-layout pattern, mirroring the header phone menu: in a body > aside, a button[popovertarget] and its [popover] show the nav in the sidebar on wide screens (popover display: contents, button hidden) and only the button on phones; the nav opens as an anchored menu under it (the menu popover rule). No JavaScript. Tested at 1100px and 360px, with no sideways scrolling. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The default look changes (EXPECTATIONS.md section 2; roadmap chunk 23's open question, decided as the 2.0 default with no opt-in): - Frame by role: a grid card is a box only with a link, button, or picture; feature cards are open. A fill or a border, never both (cards, stat tiles, .card filled; choice cards outlined; sidebar without its line). Shadow only on overlays and the featured card, whose border is now a 2px ring. - Plain card icons at heading size; a muted, sentence-case label above a heading; --hero-background: none by default (the variable stays). - Near-neutral grays: chroma carried into neutrals capped at 0.012, lightness unchanged, so contrast is unchanged (tested with 10 primaries). - Nav links muted text (current page full contrast and heavier, neutral sidebar fills); table links underlined text; photo-hero nav stays full contrast. Prose links, buttons, focus keep the primary. - A blockquote is text with a rule, a callout keeps its fill. - Bands get clamp(3rem, 8vw, 6rem); hero h1 tighter tracking and more room before its paragraph (it already reached 3.5rem). - New: a price in a card, <p><strong></strong> <small>per month</small></p>, with false-match tests (prose, strong + text, <b>). Version 2.0.0 (unreleased), CHANGELOG with "Changes to existing pages", roadmap question ticked, docs and demo updated, tests rewritten for the new expectations, demo and Markdown snapshots regenerated. CDN lines stay @1 until publish (noted in the roadmap). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Found in the screenshots: TagKit's landing and pricing cards put the price in <header> under the plan name, so the pattern didn't apply. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
What visitors expect: states, banners, sticky header, menus that stay on screen
TagBrush.css 2.0: a default look that reads as designed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PRs #45–#50 were stacked, each merged into the branch below it, so none of their work reached
main. This branch ismainwith all seven stranded branches merged in, bottom of the stack first:classless-landing-patterns(Landing-page patterns, and coverage over size #44 already on main, plus Interaction, and styling from what the HTML means #45 merged into it afterwards)interaction-and-intent(Interaction, and styling from what the HTML means #45)chunk-23-later(Chunk 23, later items: choice cards, pull quotes, data, embeds, pickers #46)guide-split(Split the agent guide into an index and detail files #47)tabs(Tabs: a role="tablist" row with the selected tab underlined #48)expectations(What visitors expect: states, banners, sticky header, menus that stay on screen #49)look-2.0(TagBrush.css 2.0: a default look that reads as designed #50)There were no conflicts, and every one of those branches is now an ancestor of this one. A rebuild changed no files.
This makes
main2.0.0 (unreleased). It includes #50, the breaking change to the default look, so the next release frommainis 2.0.0. CDN lines still saytagbrush@1until then.Checks: 520 tests pass in Chromium and WebKit. Firefox can't launch in the local sandbox; CI runs it.
🤖 Generated with Claude Code