This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10911 - Datalist descendants shouldn't be barred from constraint validation
Summary: Datalist descendants shouldn't be barred from constraint validation
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2010-09-30 22:19 UTC by Mounir Lamouri
Modified: 2011-08-04 05:12 UTC (History)
9 users (show)

See Also:


Description Mounir Lamouri 2010-09-30 22:19:58 UTC
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'>

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?
Comment 1 Ms2ger 2011-03-15 19:35:15 UTC
HTML WG website?
Comment 2 Ian 'Hixie' Hickson 2011-05-07 20:43:39 UTC
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:

Status: Rejected
Change Description: no spec change
Comment 3 Michael[tm] Smith 2011-08-04 05:12:26 UTC
mass-move component to LC1