Respect time limits in ion-datetime

[oudzy]

https://guides.github.com/features/mastering-markdown/

Short description:

ion-datetime ignoring the time part inside the min and max attributes.

What to expect:

Respect the time limits provided in the min and max attributes.

Steps to reproduce:

1. add ion-datetime to an Ionic 2 app;
2. add min and max attributes with time;
3. when using the ion-datetime try to select a date out of the min and max range;
4. ion-datetime will set limits to the date but not the time.

<ion-item>
   <ion-label>dateTime input with min and max attrs</ion-label>
   <ion-datetime 
        displayFormat="MMM DD, YYYY HH:mm"
        min="2016-06-10T15:30"
        max="2017-06-10T13:30"
        [(ngModel)]="dateObj"></ion-datetime>
</ion-item> 

Ionic Version: Ionic 2 beta 8

http://plnkr.co/edit/MzqRRCy0K7TEQTWmd7I9?p=preview

[evgeniynet]

ion-datetime also doesn't even showed in IE 11

[jgw96]

Hello @oudzy ! Thanks for opening an issue with us! To bind a component to a property (like min and max) in angular 2 you use this syntax [max]. You can read more about that here on the Angular docs. Also @evgeniynet we do not support any version of Internet Explorer with Ionic 2, although we do support Edge and Windows 10 universal apps fully! Thanks everyone for using Ionic!

[oudzy]

@jgw96 Thanks for your response but i meant a different issue, binding is fine, and i have updated the pluker example to bind the values instead of the direct assignment which is already works, but the problem as described above, the component ignore the time part.

Please take a look at the updated example and try to enter an unvalid value like 30/10/2017 23:00
http://plnkr.co/edit/MzqRRCy0K7TEQTWmd7I9?p=preview

[evgeniynet]

I confirm, problem with time exists 

За час рушится Вавилон!

Четверг, 16 июня 2016 г., 18:10 +0300 от notifications@github.com notifications@github.com:

@jgw96 Thanks for your response but i meant a different issue, binding is fine, and i have updated the pluker example to bind the values instead of the direct assignment which is already works, but the problem as described above, the component ignore the time part.
Please take a look at the updated example and try to enter an unvalid value like 30/10/2017 23:00
http://plnkr.co/edit/MzqRRCy0K7TEQTWmd7I9?p=preview
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub , or mute the thread .

[jgw96]

Sorry about that @oudzy ! I read the issue wrong. Looking at this issue again.

[ghislaindj]

Hi !
It seems that the component doesn't fully ignore the min date : at first it ignores it, but as soon as you've touched it, the component seems to work fine and respect the min property.

[oudzy]

@ghislaindj That's wright but only the min and max date, not the time, the time part of input is not limited even when the component been touched.