W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2011

[whatwg] Why children of datalist elements are barred from constraint validation?

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 29 Jul 2011 17:17:08 -0700
Message-ID: <op.vzeoeuiy64w2qv@42-2-187-074.static.netvigator.com>
On Fri, 29 Jul 2011 15:20:59 -0700, Jonas Sicking <jonas at sicking.cc> wrote:
> Ah, well, then it definitely seems like we should get rid of this
> feature. The harm is definitely there in that it's adding a feature
> without solving any problem.
>
> For what it's worth, I'm not even convinced there is a problem. The
> website can always let the <select> be submitted and ignore it on the
> server if it contains a empty value, and then make the first <option>
> in the <select> look something like <option value="">You can select a
> prefilled value here</option>

If we are removing the <select> fallback feature we should also change the  
way you find <option> elements for a <datalist> element I think. That  
should be aligned with <select>: A child element search rather than a  
descendant element search.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Friday, 29 July 2011 17:17:08 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:35 UTC