Minor Changes
-
ed2d9ae: feat(DST-1551): add
DateRangePickercomponentNew
<DateRangePicker>lets users enter or select a start–end date range through a single field, mirroring<DatePicker>'s API and behaviour. Two date inputs (start/end) sit in one field group with a calendar button that opens a<RangeCalendar>in a popover on desktop and a tray on small screens. Supports per-input paste (ISO/EU/US formats),granularity(inline time segments),visibleDuration(up to three months), and the usual Marigold field props (disabled,readOnly,required,error,errorMessage,description,minValue,maxValue,dateUnavailable,width,variant,size). Adds a matchingDateRangePickertheme entry totheme-rui.
Patch Changes
-
ed2d9ae: fix(DST-1551): round the
RangeCalendarhover and focus highlight on days outside the selected rangeDays outside the selected range now round their hover and focus highlight to match the selected state, instead of showing a square highlight against the rounded endpoints. In-range cells stay square so the range fill still connects seamlessly.
-
24354a9: fix(DST-1560): correct the
@source inlinepadding safelist to the real spacing tokensThe padding safelist in
styles.cssstill used the pre-rename vocabulary{compact, tight, regular, relaxed, spacious}, but the spacing tokens were long ago renamed to{tight, snug, regular, relaxed, loose}. As a resultcompact/spaciousforce-generated dead utility classes (resolving to undefined--spacing-*vars), while the realsnug/loosetokens were never safelisted and so were unavailable in scanner-excluded stories and in the (unscanned) docs app. The leading family-less line was also stale — it predates thesquare/squish/stretchsplit.Replaced the three lines with the three inset-padding families (
square/squish/stretch) using the real size names, so utility classes likep-squish-relaxedresolve to a concrete value and the full inset vocabulary is available where the scanner can't see it. -
4d44517: fix: make Select and Menu overlay appear above Drawer on small screens
On small screens,
SelectandMenurender their options in aTray(bottom sheet). TheTrayoverlay hadz-40in the theme while theDraweroverlay usesz-50, so the tray rendered behind an open drawer and was unreachable.Moved the
z-indexfrom the theme style file into theTrayModalcomponent implementation (matching the project's z-index architecture rule), and raised it toz-50. Both theDrawerandTrayportal todocument.body; at equal z-index, DOM order determines stacking. TheTrayis always mounted after theDrawer, so it correctly appears on top. -
Updated dependencies [ed2d9ae]
-
Updated dependencies [e686474]
-
Updated dependencies [2fc7b96]
-
Updated dependencies [508ec2c]
-
Updated dependencies [4d44517]
- @marigold/components@17.9.0
- @marigold/system@17.9.0