- From: <bugzilla@jessica.w3.org>
- Date: Wed, 18 Feb 2015 09:58:35 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28044 Bug ID: 28044 Summary: Bug with "linked" datetime-local inputs min value Product: HTML WG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: HTML5 spec Assignee: dave.null@w3.org Reporter: patrick.boguet@gmail.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org 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 ? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 18 February 2015 09:58:37 UTC