W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2010

[whatwg] input element list attribute and filtering suggestions

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 31 Dec 2010 09:07:37 -0800
Message-ID: <AANLkTinGUMqbE0gnTUTRpcamXPzVA8YAXhajGacDoDtO@mail.gmail.com>
On Fri, Dec 31, 2010 at 5:50 AM, Anne van Kesteren <annevk at opera.com> wrote:
> On Fri, 31 Dec 2010 01:36:44 +0100, Ian Hickson <ian at hixie.ch> wrote:
>> The thing that makes this different than "Google suggest"-style UI is that
>> in the latter case you need a script that continually polls for more
>> appropriate suggestions and updates the list -- for this kind of thing
>> we'd probably want to use a direct API, we wouldn't want to have scripts
>> have to poke at the <datalist> DOM in real time.
> For the "Google suggest"-style UI you also need to be able to show more than
> just options. Google has buttons, tables, images, and all kinds of other
> things in its dropdown.

Indeed. But google is fairly alone in this design. I've seen plenty of
other websites with dynamically populated autocomplete lists which
doesn't put buttons in the list itself. For example the email
autocomplete in bugzilla.mozilla.org.

/ Jonas
Received on Friday, 31 December 2010 09:07:37 UTC

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