# @spark-web/date-picker ## 5.3.2 ### Patch Changes - [#847](https://github.com/brighte-labs/spark-web/pull/847) [`b68587f`](https://github.com/brighte-labs/spark-web/commit/b68587f08c703b77885883c505cc13dd271df2a4) Thanks [@jacobporci-brighte](https://github.com/jacobporci-brighte)! - Stop the untouched `DD/MM/YYYY` mask reading as an entered date. The mask is seeded into the input's `value` on focus rather than left in `placeholder`, so the input's `::placeholder` tone cannot reach it — a freshly focused, empty field showed `DD/MM/YYYY` in full-strength content colour. While the mask is untouched it now renders in the `foreground.placeholder` tone. As soon as the first digit is typed the value returns to full strength, since the field genuinely holds content from that point on. Before focus the native placeholder applies, which `@spark-web/text-input` now tones down. - Updated dependencies [[`b68587f`](https://github.com/brighte-labs/spark-web/commit/b68587f08c703b77885883c505cc13dd271df2a4)]: - @spark-web/text-input@6.1.1 ## 5.3.1 ### Patch Changes - [#835](https://github.com/brighte-labs/spark-web/pull/835) [`0781558`](https://github.com/brighte-labs/spark-web/commit/07815585304c5426cc87e87c865f3055950cc028) Thanks [@tyren-t-brighte](https://github.com/tyren-t-brighte)! - Fix the `DD/MM/YYYY` mask behaving like an editable value. The mask is seeded into the input as a real value on focus, but `onFocus` only fires on the focus transition — so any later caret move left the caret wherever it landed. Clicking to the right of the mask put the caret at the end, and typing then filled the **year** segment from the right (`DD/MM/YYYY` → `DD/MM/1YYY`) instead of the day. The keyboard reached the same broken state without a mouse: `End`, or enough `ArrowRight`s, then typing. Clicks and navigation keypresses now keep the caret at the first unfilled slot. Selections are left alone so a segment can still be highlighted and overwritten (drag or Shift+Arrow), moving back into an already-typed segment is untouched, and once the date is complete the caret is left entirely alone. Focusing the field still places the caret at the start, unchanged from before. Also fixes a related issue where a partially typed mask survived blur: `onBlur` cleared the input only on an exact match to the full mask, so typing `12` and clicking away left `12/MM/YYYY` on screen as dark, entered-looking text while `onChange` had emitted `undefined`. Any incomplete mask is now cleared on blur. No API change — props, `value` and `onChange` are unaffected, and the input's rendered value is unchanged in every state that was already reachable. - Updated dependencies [[`0781558`](https://github.com/brighte-labs/spark-web/commit/07815585304c5426cc87e87c865f3055950cc028)]: - @spark-web/text-input@6.1.0 ## 5.3.0 ### Minor Changes - [#829](https://github.com/brighte-labs/spark-web/pull/829) [`783fa47`](https://github.com/brighte-labs/spark-web/commit/783fa47dd2175be789a824d61090e92047f2b78d) Thanks [@tyren-t-brighte](https://github.com/tyren-t-brighte)! - Add month and year dropdowns to the calendar header. The header now shows tappable month and year controls flanked by full prev/next arrow buttons (44×44 touch targets). Tapping the month or year opens a full-card list — the selected option is centred with a couple of options above and below, and the list scrolls; picking one jumps the calendar there. While a dropdown is open the arrows are hidden and the other control is disabled, and it collapses on selection, on tapping the control again, or on Escape/outside click. Two optional props, `fromYear` and `toYear`, bound the year list (defaulting to `minDate`/`maxDate`'s years, else 100 years back to 10 years forward). The range only affects the year list — day navigation and typed input are unchanged, and the currently shown year is always included, so existing usage keeps working. Note: this changes the calendar header markup (the plain "Month Year" label becomes arrow buttons + two dropdown controls). If you have visual snapshots of the calendar, expect to re-approve them. `react-select` is now a runtime dependency of this package (the same one `@spark-web/combobox` uses), powering the option list. ## 5.2.1 ### Patch Changes - [#810](https://github.com/brighte-labs/spark-web/pull/810) [`208bd76`](https://github.com/brighte-labs/spark-web/commit/208bd766d2007c5f7c222b200ffcd7af9b60b6c3) Thanks [@tyren-t-brighte](https://github.com/tyren-t-brighte)! - Add the vendor-admin surface to the machine-readable design system: - New vendor-admin surface rules (`patterns/vendor-admin/CLAUDE.md`): layout shell, `Heading level="2"` page title, spacing/density, side-panel-vs-full-page detail interaction, infinite-scroll-vs-pagination list loading, bulk-action toast, badge tone mapping, and role/feature-flag gating. - New vendor-portal consumer overlay (`patterns/vendor-admin/vendor-portal.md`) documenting the repo's local substitutions (TablePagination, SidePanel, MultiselectCheckbox, FormField, SettingsPanel, FlashMessage, InfoBox) and data conventions. - Two new vendor-admin screen patterns: `list-page.md` (filterable list with side-panel detail, infinite scroll or pagination, and bulk-action toast) and `form-page.md` (centered, sectioned settings/create form), each with a mechanically-checkable validation checklist; both registered in the surface registry. - New component AI-context docs (`CLAUDE.md`, now published) for checkbox, date-picker, currency-input, container, and divider — the components the vendor-admin patterns require. - Updated dependencies [[`208bd76`](https://github.com/brighte-labs/spark-web/commit/208bd766d2007c5f7c222b200ffcd7af9b60b6c3), [`208bd76`](https://github.com/brighte-labs/spark-web/commit/208bd766d2007c5f7c222b200ffcd7af9b60b6c3)]: - @spark-web/a11y@5.3.1 - @spark-web/text-input@6.0.3 - @spark-web/heading@5.2.1 - @spark-web/icon@5.1.1 ## 5.2.0 ### Minor Changes - [#667](https://github.com/brighte-labs/spark-web/pull/667) [`80d9c15`](https://github.com/brighte-labs/spark-web/commit/80d9c156a40bbcd2b1a91a2d0403b3c8e9b47b4e) Thanks [@Leo704099](https://github.com/Leo704099)! - Support react 17 to 19 ### Patch Changes - Updated dependencies [[`80d9c15`](https://github.com/brighte-labs/spark-web/commit/80d9c156a40bbcd2b1a91a2d0403b3c8e9b47b4e)]: - @spark-web/text-input@6.0.0 - @spark-web/heading@5.2.0 - @spark-web/button@5.6.0 - @spark-web/field@5.3.0 - @spark-web/stack@5.1.0 - @spark-web/theme@5.13.0 - @spark-web/a11y@5.3.0 - @spark-web/icon@5.1.0 - @spark-web/text@5.3.0 - @spark-web/box@6.0.0 ## 5.1.2 ### Patch Changes - [#698](https://github.com/brighte-labs/spark-web/pull/698) [`814b373`](https://github.com/brighte-labs/spark-web/commit/814b373cbe9fcf0757738c78eef6b516624df62c) Thanks [@michtntbrighte](https://github.com/michtntbrighte)! - Bump version - Updated dependencies [[`814b373`](https://github.com/brighte-labs/spark-web/commit/814b373cbe9fcf0757738c78eef6b516624df62c)]: - @spark-web/box@5.2.2 - @spark-web/button@5.5.2 - @spark-web/field@5.1.3 - @spark-web/heading@5.1.3 - @spark-web/stack@5.0.2 - @spark-web/text@5.2.3 - @spark-web/text-input@5.3.2 - @spark-web/theme@5.12.1 ## 5.1.1 ### Patch Changes - Updated dependencies [[`1995db7`](https://github.com/brighte-labs/spark-web/commit/1995db7f4342803732c7648ab3ca6d32442cc347)]: - @spark-web/theme@5.12.0 - @spark-web/button@5.5.1 - @spark-web/field@5.1.2 - @spark-web/heading@5.1.2 - @spark-web/stack@5.0.1 - @spark-web/text@5.2.2 ## 5.1.0 ### Minor Changes - [#652](https://github.com/brighte-labs/spark-web/pull/652) [`d93c2a5`](https://github.com/brighte-labs/spark-web/commit/d93c2a5689e217f69002c78ba6cfb77561fc6c1d) Thanks [@ralcoriza-brighte](https://github.com/ralcoriza-brighte)! - Expose autoComplete prop to input components ### Patch Changes - Updated dependencies [[`d93c2a5`](https://github.com/brighte-labs/spark-web/commit/d93c2a5689e217f69002c78ba6cfb77561fc6c1d)]: - @spark-web/text-input@5.3.0 ## 5.0.0 ### Major Changes - This release of spark-web standardises the version across all packages to be **`v5`**, primarily signifying the switch from `@emotion/css` to `@emotion/react` as one of the key dependencies of the entire library, in order to support server-side rendering / SSR. This release also introduces support for theming, to allow for more co-branded experiences across our web applications. It also supports component-level theming for `