-
Notifications
You must be signed in to change notification settings - Fork 27.4k
ngModelOptions for date input using min attribute #11221
Comments
I think this is probably an issue with the min and max validators not using the convertTimezoneToLocal function on value if timezone is set. (If the min and max attributes are supposed to adjust to the timezone in ngModelOptions.) angular.js/src/ng/directive/input.js Line 1144 in ddc6120
|
@shahata can you take a look at this? Thanks! |
Yeah, I'll take a look probably tomorrow |
is it still an issue? |
Top input is invalid because min attribute sees the date as before the acceptable min date. The min/max attributes are not respecting ngModelOptions' timezone setting. |
I see. |
Ohh. Yeah. I should have demo'd a max issue as well to cover both sides of UTC. Sorry. |
Duplicate of #16342 |
I am running into an issue, and I am not sure if it is expected behavior or not. I would expect the min attribute on a date input to adjust to UTC when ngModelOptions is set for that, but it is not doing it. Below of a Plunker that outlines what I am talking about.
http://embed.plnkr.co/IjCPztKVsbERDJaNO160/preview
The text was updated successfully, but these errors were encountered: