This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Hi, I have a problem with two datetime-local inputs which are "linked" (that means my first input sets a min date value for the second one). I use the Chrome mobile browser on an Android tablet for a web application in HTML5. I choose a first date : 2015/02/18 10:15:00 from the first input (format 2015/02/18T10:15:00). Then, I define this date for the min date in my second input (with document.getElementById('mySecondInput').min = firstDate) When I want to choose my second time, the picker time starts at 11:15. So, it's impossible to set a time before 11:15 (example 10:45). It seems that the min value is used for the hours and not for the minutes. Is that a standard behavior for the datetime-local input ? Why not start the min value with firstDate + 1 minute instead of firstDate + 1 hour ?
datetime and datetime-local indicates: [[ The step attribute is expressed in seconds. The step scale factor is 1000 (which converts the seconds to milliseconds, as used in the other algorithms). The default step is 60 seconds. ]] so it seems to me that the implementation is incorrect. Did you check with other implementations to see which step they take?
HTML5.1 Bugzilla Bug Triage: this is an implementation bug. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!