chore(sync): record the checkbox border-default swap as a no-op - #502
Merged
Conversation
Ports nuxt/ui `9bdb89b0` (#6884) as a no-op: one token across five slots,
`border-muted` → `border-default` on the `card` and `table` variants of
Checkbox, CheckboxGroup and RadioGroup.
Neither token is on our side of that line. All five fork equivalents read
`border border-(--ui-color-design-outline-na-stroke)` — the Air design system's
outline stroke, annotated `@memo style-outline-no-accent` — checked individually
at `checkbox.ts:63`, `checkbox-group.ts:48,56` and `radio-group.ts:69,77`. There
is no `border-muted` to replace and no `border-default` to replace it with.
The `${hover}bg-elevated/50` fragment in the same string is not ours either. It
arrived upstream in `07f3fe8d` as part of the hover/checked/focus palette
refresh, which this fork declined by maintainer decision when that commit was
ported (#464) — our `card` and `table` carry their own treatment in air tokens.
So this commit adjusts a line that, on our side, was already deliberately
different.
Stated precisely rather than as "we don't use those tokens": we do use
`border-default` in `dropdown-menu.ts` and `sidebar.ts`, and `border-muted` in
`prose/prompt.ts`. The tokens exist here; they are simply not what these five
slots are written in.
Nothing to port, and nothing deferred — taking it would mean first adopting the
palette refresh this fork chose not to.
Ledger: cursor → `9bdb89b0` (upstream HEAD), parity snapshot refreshed.
3 tasks
IgorShevchik
added a commit
that referenced
this pull request
Aug 27, 2026
The entry was written with `pending-merge` because the PR carrying it had not merged yet; it now points at #502 and its squash SHA `0e2cb6e0`. No entry in the ledger is left unreconciled, and the cursor `9bdb89b0` is upstream HEAD. Bookkeeping only — no source, test or docs change. Co-authored-by: Shevchik Igor <noreply@anthropic.com>
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
2 participants
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.
Linked issue
Sync with
nuxt/ui@v4—9bdb89b0(nuxt/ui#6884). After this the cursor is at upstream HEAD.Type of change
Description
Upstream swaps one token across five slots —
border-muted→border-defaulton thecardandtablevariants of Checkbox, CheckboxGroup and RadioGroup, with 168 snapshot lines following.Neither token is on our side of that line. All five fork equivalents read:
the Air design system's outline stroke, annotated
@memo style-outline-no-accentincheckbox.ts. Checked individually:checkbox.ts:63,checkbox-group.ts:48,56,radio-group.ts:69,77. There is noborder-mutedto replace and noborder-defaultto replace it with.The
${hover}bg-elevated/50fragment in the same string is not ours either. It arrived upstream in07f3fe8das part of the hover/checked/focus palette refresh, which this fork declined by maintainer decision when that commit was ported (#464) — ourcardandtablecarry their own checked and hover treatment in air tokens. So this commit adjusts a line that, on our side, was already deliberately different.Worth stating precisely rather than as "we don't use those tokens": we do use
border-defaultelsewhere —dropdown-menu.tsandsidebar.ts(×4) — andborder-mutedinprose/prompt.ts. The tokens exist here; they are simply not what these five slots are written in.Nothing to port, and nothing deferred: taking it would mean first adopting the palette refresh this fork chose not to.
Verification
Ledger only — no source, test or docs change. Cursor →
9bdb89b0, which is upstream HEAD; parity snapshot refreshed to it with zero package differences, andtest/utils/dep-parity.spec.tspasses in full (22 assertions).Checklist
Generated by Claude Code