W3C home > Mailing lists > Public > www-validator-cvs@w3.org > April 2015

[Bug 28428] OPTION element in DATALIST element can be empty, but validator say no

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Apr 2015 17:48:02 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-28428-169-3eYC4xmXK1@http.www.w3.org/Bugs/Public/>

--- Comment #4 from Michael Benjamin <mbb448@gmail.com> ---
(In reply to Michael[tm] Smith from comment #3)

Thank you again for taking the time to respond.

I mentioned that the spec wasn't clear or definitive because, if what you're
saying is correct about the language, then the spec very clearly contradicts
itself. See the first code example here:

In this example, there is no LABEL attribute and no text content in the OPTION
elements. This code would not pass validation. Yet the W3C Recommendation
provides this example for instructional purposes.

Regarding examples -- from various reputable and reliable sources -- with empty
OPTION elements, this seems to be the norm across all web tutorials. There are
no cases I have found where the OPTION element in a DATALIST uses text content
or the LABEL attribute. This is probably because the spec -- as you can see
from the link above -- is unclear and possibly misleading.

I'll consider your advice to file a bug report on this. In the meanwhile, I
hope you'll consider allowing validation to pass for code structured in
conformance with the examples in the W3 Recommendation. Thank you, again.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 10 April 2015 17:48:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:03:26 UTC