-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
Time range selection (min, max) not working correctly #43
Comments
I see. I'll check it |
Fixed, sorry for so long. Update to the latest version and try |
I see, I guess it’s because of refactoring. I’ll figure out what the problem is and fix ASAP |
Update to 2.6.3 and try it out please |
Hi Agranom! |
Oh, sorry. I've aready found the problem and fix it in the next release with other bugfixes |
Sorry but in the above screenshot I'm using version 2.6.3 and I can't see more updated version than that. |
I haven't publish yet ) |
Hi, i've the some problem of @Zaheer211 . It's solved? |
Not solved yet. Waiting for the fixed version. |
Already published. Try :) |
Have you tried yet? |
Sorry, my fault. Already fixed it. Update to 2.6.5 pls |
Thanks - I'll check and let you know. |
Have you checked? |
Hey Agranom! This issue seems resolved in version 2.8.0. Thanks for your great support, I'm closing it. |
We're using ngx-material-timepicker in our project and came across an issue in range time selection.
Here is input element for time-picker.
<input matInput type="text" [ngClass]="{'time myInput': true, smallFont: popupView}" formControlName="time" [ngxTimepicker]="picker" placeholder="Add time" min="09:00 am" max="03:00 pm" readonly>
<ngx-material-timepicker [ngClass]="{'timePicker': true}" (timeSet)="onTimeSet($event)" #picker></ngx-material-timepicker>
Expected:
It should allow to select anytime between 09:00 am to 03:00 pm.
Problem:
12:00 pm to 12:59 pm can't be selected. Event though it lies within the above range.
Two screenshots are attached to support above argument.
Thanks in advance for any help!
The text was updated successfully, but these errors were encountered: