-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add readonly support to input-date-picker & input-time-picker #1947
Comments
@paulcpederson @eriklharper @macandcheese We don't have |
No, we should probably have |
Yeah agree.. right now you can add readonly and the styles will correctly apply, and the attribute will render on the child input element... however it’s not defined as a custom prop - it’s just getting spread if present - so it’s not getting documented. Should add that so it’s on the calcite input and to the point of the issue probably anything that wraps one like a date, or time input. |
I'm in favor of removing spread attributes as a general principle. Best to always explicitly define the attributes being used and supported. |
Yeah, we shouldn't be passing everything into the internals of the component. |
@benelan can we squeeze this one for this release? |
Sure, triaged! |
@Elijbet Can you look at this one for this release? |
Sure thing. |
Installed and assigned for verification. |
Verified |
Description
Add read-only support to the input date and time pickers.
Acceptance Criteria
readOnly
prop is addedreadonly
on the input to true and prevent the popover support components from being displayed.Which Component
calcite-input-date-picker
calcite-input-time-picker
Example Use Case
Readonly: When the date/time has already been set and can not be changed.
Additional info
https:/Esri/calcite-components/blob/master/src/components/input/input.tsx#L215-L220
#2734
The text was updated successfully, but these errors were encountered: