This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I agree that a child of a datalist element should not block the form submission. However, I'm wondering why do we care about this particular edge case when there are a lot of situations where an element can be invalid without any possible action from the user. There is this backward-compatibility friendly use of datalist that requires to have a select inside a datalist like: <input list='d'> <datalist id='d'> <select> <option>Option1</option> </select> </datalist> However, this use case doesn't justify barring from constraint validation because the only situation where that would be needed is if <select> is required and the first option is making select suffering from value missing. However, using required in a backward-compatibility path would be wrong and using required wouldn't follow how lists are working (ie. you don't _have_ to select something). Is there any other reasons I'm missing?
HTML WG website?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-May/031426.html
mass-move component to LC1