Examples
These examples show the styled wrapper in its default plain-CSS presentation and in a theme-aware Tailwind shell across common use cases.
Form usage
Month Daypicker fits naturally into forms where a recurring date — birthday, anniversary, or annual deadline — is one submitted field.
Month Daypicker form usage
Default wrapper
Stock behavior with editable MM-DD input and month-then-day calendar navigation.
Default wrapper (Plain-CSS)
The default wrapper picks up the theme contract without extra utility classes.
Default wrapper (Tailwind CSS)
Tailwind can own the outer surface while semantic tokens keep light, dark, and custom themes in sync.
Disabled state
The entire field — input, trigger, and calendar — is inert when disabled is true.
Disabled state (Plain-CSS)
Disabled styling flows through the [data-disabled] state hook on the host and cells.
Disabled state (Tailwind CSS)
Read-only
The text field is read-only but the calendar popup remains accessible for selection.
Read-only (Plain-CSS)
Manual typing is blocked but calendar-based selection still commits a value.