Several distinct regressions/latent bugs surfaced via the DatePicker, all the same
root: parts wrongly typed as the interactive `trigger`/`item` archetype pulling
button/listbox chrome they should not have.
- Field overlay triggers (date/time/color picker, date-range) are NOT buttons:
new `field-trigger` archetype; the picker trigger soma overrides the popover's
generic `trigger` archetype with it. popover.css no longer applies the generic
popover-button envelope to `[data-field-control-trigger]` (composing IconButton
flipped CSS load order, so the button border/bg bled into the flush field icon).
- The field input drops its padding on the trigger side (logical → LTR + RTL):
`[data-archetype='input']:has([data-field-control-trigger]) { padding-inline-end: 0 }`
— the trigger sits flush instead of behind the full text padding.
- Calendar/range/month/year-grid Cell + GridRow + Day declared `archetype: 'item'`,
which shipped the listbox-row chrome: 6px cell padding (tall rows), a full-week
hover band, and `[data-archetype='item'][data-selected]` (higher specificity)
OVERRODE the calendar's accent fill so the selected day showed the menu tint
instead of solid accent. These are display gridcells, not menu items — archetype
removed; the Day keeps its bespoke `[data-calendar-day]` styling.
Verified in browser: DatePicker now matches the standalone Calendar (32px rows,
solid-accent selected day, no week-band hover, flush calendar-icon trigger).
morfo 62/62. Excludes words/palabras/chronos.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
active-uix
parent
a4d86edb24
commit
f822d6e4dd
Loading…
Reference in new issue