You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
Describe the bug
When using fixedStart or fixedEnd the time picker still allows to customize the time of the fixed date. In this case, it should either block the time selection, or a second prop such as fixedStartTime/fixedEndTime would be appreciated. The time input should then be disabled or hidden altogether.
To Reproduce
Steps to reproduce the behavior:
Create a datetimepicker component
Set the range=true & fixedStart=true prop
Open the time selector
It is now possible to customize the start time
Expected behavior
It should not be possible to customize the time of either end when it is fixed. The time inpit should either be disabled or hidden. (Disabled would be more in line with how the date selection works, but hdden might be a bit cleaner in the UI)
Screenshots
Desktop (please complete the following information):
OS: macos 12.2.1
Browser: Google Chrome
Version: 98.0.4758.102 (Official Build) (x86_64)
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Describe the bug
When using
fixedStart
orfixedEnd
the time picker still allows to customize the time of the fixed date. In this case, it should either block the time selection, or a second prop such asfixedStartTime
/fixedEndTime
would be appreciated. The time input should then be disabled or hidden altogether.To Reproduce
Steps to reproduce the behavior:
range=true
&fixedStart=true
propExpected behavior
It should not be possible to customize the time of either end when it is fixed. The time inpit should either be disabled or hidden. (Disabled would be more in line with how the date selection works, but hdden might be a bit cleaner in the UI)
Screenshots
Desktop (please complete the following information):
Additional context
n/a
The text was updated successfully, but these errors were encountered: