W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

[whatwg] input element list attribute and filtering suggestions

From: Scott González <scott.gonzalez@gmail.com>
Date: Fri, 20 Jan 2012 20:07:54 -0500
Message-ID: <CAO8i3ie5-fB1DmAWABgLFrZUaa-6OOvZ7NzGjuaE+ODMvzHGpw@mail.gmail.com>
On Fri, Jan 20, 2012 at 6:41 PM, Ian Hickson <ian at hixie.ch> wrote:

> On Mon, 1 Aug 2011, Aryeh Gregor wrote:
> > On Fri, Jul 29, 2011 at 7:24 PM, Ian Hickson <ian at hixie.ch> wrote:
> > > My overarching point, however, is that this is a UI issue, and not an
> > > authoring issue.
> >
> > The overarching counterpoint is that in-page UI *is* an authoring issue,
> > because authors want to control exactly how their page looks and
> > behaves.  Browser/chrome UI issues shouldn't be standardized, but page
> > UI issues absolutely should (at least in many cases).
>
> I disagree with this, at least in terms of a general guiding principle.
>

I agree with Ian. I'm not sure how/why something like autocomplete should
be treated different than select elements or alert dialogs. If you need a
lot of control over the appearance or functionality, don't rely solely on
native controls; enhance them with custom JS and CSS. I don't think it's
reasonable for standards to try to address all appearance and functionality
issues. The native implementations should work for everyone and be "good
enough" for the majority. The rest is up to page, library, and framework
authors.
Received on Friday, 20 January 2012 17:07:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC