Skip to content

Update VCP to v3.2.0, split calendar/datepicker components - #42856

Open
mdo wants to merge 3 commits into
v6-devfrom
mdo/vanilla-calendar-pro-3.2.0
Open

Update VCP to v3.2.0, split calendar/datepicker components#42856
mdo wants to merge 3 commits into
v6-devfrom
mdo/vanilla-calendar-pro-3.2.0

Conversation

@mdo

@mdo mdo commented Aug 20, 2026

Copy link
Copy Markdown
Member
  • Bump vanilla-calendar-pro to v3.2.0 in package.json, the lockfile, and the CDN URL in config.yml
  • Put the column grid on the new month and year row elements. VCP 3.2.0 wraps months and years in row and cell elements to fix their ARIA grid structure, which moves the grid off the container and collapses both views to three rows
  • Split the calendar grid out of _datepicker.scss into a new scss/_calendar.scss with its own token map. The datepicker now layers the popup surface onto a bare calendar, instead of inline calendars undoing the popup styling
  • Style a calendar with the --calendar-* tokens and the popup with the --datepicker-* tokens. The popup passes its padding down through --calendar-padding
  • Add a Calendar docs page and its sidebar entry. It points at the datepicker for options, methods, and events, because the calendar has no JavaScript of its own
  • Document the token split and the Shadow DOM caveats on the Datepicker page
  • Add unit tests that pin the month and year markup and the data-vc-input popup/inline distinction, because this regression was invisible to the suite
  • Add inline calendar coverage to the datepicker visual test

Fixes #42836

mdo added 2 commits August 13, 2026 10:23
VCP 3.2.0 wraps the months and years in row and cell elements to fix
their ARIA grid structure. That change moves the grid columns off the
container, so put the column grid on the new row elements. The month and
year views otherwise collapse to three rows.

Also split the calendar grid out of the datepicker into its own Sass
partial and token map. The datepicker now layers the popup surface onto a
bare calendar, instead of inline calendars undoing the popup styling. Use
the `--calendar-*` tokens to style a calendar and the `--datepicker-*`
tokens to style the popup.

Add unit tests that pin the month and year markup, because this
regression was invisible to the suite.

Closes #42836
The calendar now has its own Sass partial and token map, so document it
apart from the datepicker. The page covers the inline calendar, the
`--calendar-*` tokens, and the color modes.

Point at the datepicker for options, methods, and events, because the
calendar has no JavaScript of its own.
The bundle build inlines Vanilla Calendar Pro, so the v3.2.0 row and cell
markup adds 555 bytes gzipped to `bootstrap.bundle.min.js`. That puts the
file at 55.75 kB, above the 55.5 kB budget.
@mdo mdo changed the title Update Vanilla Calendar Pro to v3.2.0 Update VCP to v3.2.0, split calendar/datepicker components Aug 22, 2026
@coliff

coliff commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Inbox

Development

Successfully merging this pull request may close these issues.

2 participants