On 6/5/2014 3:05 AM, whatwg-requ...@lists.whatwg.org wrote:
On Tue, Jun 3, 2014 at 3:26 AM, Daniel Morris
daniel+wha...@honestempire.com wrote:
Hello,
With existing assistive technology such as screen readers, and more
recently the pervasiveness of new technologies such as Siri and Google
Hello,
Is it intentional that there is no HTMLSelectElement.autocomplete IDL
attribute[1]? Both input[2] and textarea[3] have it so there is currently
inconsistency.
Thanks,
Matthew Noorenberghe
[1] http://www.whatwg.org/specs/web-apps/current-work/#the-select-element
[2]
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
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
On Wed, Jun 4, 2014 at 7:16 PM, Ian Hickson i...@hixie.ch wrote:
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 Wed, 4 Jun 2014, Dan Beam wrote:
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
