This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
input[type="date"] validity doesn't change when min/max change #6755
Description
While creating the jsfiddle example in my previous issue, I noticed that the validity of the date input doesn't get updated when the values of min/max change.
Might just need a fix similar to: #6369
Edit:
Though, the validity of the date input does get updated if you make a change to the input after min/max are changed.
Activity
[-]input[type="date"] min/max as date objects[/-][+]input[type="date"] validity doesn't change when min/max change[/+]matsko commentedon Aug 28, 2014
I've made some progress on this and my local code works for string-based date values (the first example in your demo). But the pure date object min/max value stuff doesn't work yet. I will resume the bug fix next week once I get someone to help me understand
$interpolate(since that needs to be patched first).fix(ngModel): revalidate the model when min/max expression values cha…
fix(ngModel): revalidate the model when min/max expression values cha…
fix(ngModel): revalidate the model when min/max expression values cha…
fix(ngModel): properly parse min/max date values as strings
fix(ngModel): properly parse min/max date values as strings for date …
matsko commentedon Sep 4, 2014
This should now be working on master.
matsko commentedon Sep 4, 2014
PS your example code should be
max="{{ maxDt }}"andmin="{{ minDt }}"(you forgot the curly brackets)matsko commentedon Sep 4, 2014
You're better off using ng-min and ng-max since the date won't be converted to string and back like what happens with min and max while using expressions.