- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 29 Aug 2013 19:57:03 +0000 (UTC)
- To: Kurosawa Takeshi <taken.spc@gmail.com>, "Michael[tm] Smith" <mike@w3.org>
- Cc: whatwg@whatwg.org
On Thu, 18 Jul 2013, Kurosawa Takeshi wrote: > > I noticed inconsistency between datalist element example and option > element content model. > > In a datalist element's code example, there are option elements which > don't specify label attribute and are empty. > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-datalist-element > > > <label> > > Sex: > > <input name=sex list=sexes> > > <datalist id=sexes> > > <option value="Female"> > > <option value="Male"> > > </datalist> > > </label>> > > However option element section prohibits such condition. > > > The label content attribute, if specified, must not be empty. If the > > attribute is not specified, then the element itself must not be empty. > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-option-element > > My question is which one is correct: the code example or the option > element section. I corrected the spec on this in response to the bug you filed: On Sat, 17 Aug 2013, Kurosawa Takeshi wrote: > > Bug 22994 - Clarify option element's label must be a non empty string. > https://www.w3.org/Bugs/Public/show_bug.cgi?id=22994 If you could respond to comment 3 on that bug, that'd be great. Note that if you post to this list, there's no point also filing a bug. I'll get to the feedback either way eventually. Cheers, -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 29 August 2013 19:57:29 UTC