# Changelog
All notable changes to this project are documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
## [1.3.2] - 2026-08-24
### Fixed
- **`buildDayOptions()` showed an extra day (or ignored the day cutoff
entirely) whenever the allowed upper bound fell before the 10th.** The day
dropdown is built from two ranges — a single-digit loop (`01`-`09`) and a
double-digit loop (`10`-`31`) — normally clamped so together they cover
`[start1, end2]`. A leftover normalization step, `if (start2 > end2) {
end2 = start2; }`, ran whenever the true upper bound (`end2`, computed from
`allowFuture`/`minAge`/`maxDate`) landed below `10`: it forced `end2` back
up to `10` instead of leaving the now-empty double-digit loop alone, and
the single-digit loop's own end (`end1`, hardcoded to `9`) was never
clamped down to `end2` in the first place. In practice, with
`allowFuture: false`, picking any month/year that resolves to "today" (or
any `maxDate` whose day was under `10`) always produced every day from
`01` through `10` — e.g. on Nov 1st the day dropdown offered `01`-`10`
instead of just `01`; on Nov 9th it offered `01`-`10` instead of `01`-`09`.
Replaced both leftover lines with a single `if (end1 > end2) { end1 =
end2; }`, which clamps the single-digit loop down to the true cutoff and
lets the double-digit loop stay empty when the whole allowed range sits
below `10`.
- **Selecting the year wiped out an already-picked day/month.** Cascading
resets on `year`/`month` change (`bindChangeEvent()`) unconditionally
cleared the downstream dropdown(s) instead of only clearing them when the
existing selection was no longer valid for the newly rebuilt options. For
`displayFormat: 'dmy'` in particular, this meant a user filling the form
left-to-right (day, then month, then year) had their day and month wiped
the moment they picked a year. Added `optionsHaveValue()` and used it to
re-select the previous day/month value when it still exists in the
rebuilt option set, only falling back to a reset when the prior
selection is genuinely no longer valid (e.g. Feb 29 selected, then the
year changes to a non-leap year).
### Changed
- Added open-issues / open-pull-requests badges to `README.md`, sourced
from the GitHub repo already referenced by `package.json`'s
`repository`/`bugs` fields.
## [1.3.1] - 2026-08-17
### Fixed
- **Crash on non-`` targets without `defaultDate`.** Initializing the
plugin on a container element (e.g. a `
`) without an explicit
`defaultDate` option threw `TypeError: Cannot read properties of null
(reading 'split')` inside `processDefaultDate()`. The input-element code
path back-filled `defaultDate` from the field's value, but the container
path never did, so `defaultDate` stayed `null` and was unconditionally
`.split()`'d. `processDefaultDate()` now returns empty day/month/year parts
when no default date is set.
- **`destroy()` didn't clean up on container targets.** When the plugin was
initialized on a non-`` element, calling `.dropdownDatepicker('destroy')`
only removed the internal jQuery data reference — the generated `