- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 5 Jun 2014 02:16:20 +0000 (UTC)
- To: Matthew Noorenberghe <MattN+whatwg@mozilla.com>, Luis Farzati <lfarzati@gmail.com>, Dan Beam <dbeam@chromium.org>
- Cc: whatwg@lists.whatwg.org, Ilya Sherman <isherman@chromium.org>, Evan Stade <estade@chromium.org>
On Wed, 4 Jun 2014, Matthew Noorenberghe wrote: > > Is it intentional that there is no HTMLSelectElement.autocomplete IDL > attribute? Both <input> and <textarea> have it so there is currently > inconsistency. Woops. Totally an oversight on my part. When I added autocomplete to select recently, I forgot to fix that. Fixed. Thanks. On Wed, 4 Jun 2014, Luis Farzati wrote: > > I would like to insist on the datalist proposition I posted on this list > (didn't caught any interest, though). > > A datalist for select would enable to have the contents of a select > defined externally, and would also enable the reuse of this data. > > I don't see why datalist can be applied to an input and not to a select. Don't worry, your e-mail is in the queue! Requests for features tend to take a bit longer for me to deal with than simple bug reports, though. On Wed, 4 Jun 2014, Dan Beam wrote: > > It'd be nice to avoid more attribute accessors (and encourage authors to > use getAttribute() instead), but if <input> and <textarea> have them we > should probably be consistent. Can you elaborate on the cost of attribute accessors? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 5 June 2014 02:16:45 UTC