AB Calendar
Standalone native date input + optional picker popup (lower-level than ab-date-field).
HTML tag: c-ee3f472b1e9914eee88e08978921526ef
When to use
Section titled “When to use”- standalone date input without form field chrome
- embedded calendar control with trigger slot
- not the primary labeled form date field
| Prop | Type | Default | Description |
|---|---|---|---|
value | String | “ | |
min | String | “ | |
max | String | “ | |
disabled | Boolean | false | |
readonly | Boolean | false | |
clearButtonVisible | Boolean | false | |
firstDayOfWeek | Number | ||
lang | String | en | |
opened | Boolean | false |
- Bind .value as YYYY-MM-DD string; change event detail is the new value string.
- min/max/disabled/readonly/clearButtonVisible/firstDayOfWeek/lang/opened tune UX.
- trigger slot can customize opener; show() opens picker.
- In forms prefer ab-date-field (label, validation, display_format, value-changed).
Events
Section titled “Events”| Event | Detail |
|---|---|
change | value: String |
Methods
Section titled “Methods”| Signature | Description |
|---|---|
show() |
What to avoid
Section titled “What to avoid”Do not use in labeled entity forms when ab-date-field fits. Do not expect value-changed — this host uses change. Not for datetime/timezone (ab-timestamp family).
Example
Section titled “Example”<c-ee3f472b1e9914eee88e08978921526ef .value=${date} .min=${minDate} @change=${e => date = e.detail}></c-ee3f472b1e9914eee88e08978921526ef>