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
Consider invoking stepDown for <input type=time max=17:00 step=900>. Blink sets the value to 00:00 while Gecko computes 23:45.
According to stepDown, we subtract 15 minutes from zero obtaining a negative value. The element has no minimum and -00:15 is less than 17:00. In step 11 we then determine the new element value as
a valid time string that represents the time that is input milliseconds after midnight on a day with no time changes
This problem would also arise if there was no max attribute, right?
Although I suppose the max attribute raises the question of whether 16:45 could be a reasonable answer. (I actually think that it would be, but that matches nobody and might be tricky to define.)
It also seems that valueAsNumber can enter this same code path so we have to deal with negative values here somehow anyway.
What is the issue with the HTML Standard?
Consider invoking
stepDown
for<input type=time max=17:00 step=900>
. Blink sets the value to 00:00 while Gecko computes 23:45.According to stepDown, we subtract 15 minutes from zero obtaining a negative value. The element has no minimum and -00:15 is less than 17:00. In step 11 we then determine the new element value as
see here.
Maybe time input elements should have a default minimum of zero and default maximum of 23:59?
The text was updated successfully, but these errors were encountered: