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

Re: [whatwg] Incomplete user-input in some input types

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 8 Nov 2012 09:50:35 +0100
Message-ID: <CADnb78heLMPJOSS05bqmbs1SH8EV_a7mu1F-S1vg2O2g2sxyTA@mail.gmail.com>
To: "TAMURA, Kent" <tkent@chromium.org>
Cc: whatwg <whatwg@lists.whatwg.org>
On Thu, Nov 8, 2012 at 7:52 AM, TAMURA, Kent <tkent@chromium.org> wrote:
> C. Just validity.valid becomes false.
>    An implementation would have an internal flag like invalidUserInput, but
> it won't be exposed via IDL.
>
> C would have less impact to the standard.  If no one has concern about this
> idea, I'd like to implement C in WebKit.

I actually think exposing the UI state makes sense. It's also going to
be exposed through a selector:
http://dev.w3.org/csswg/selectors4/#user-error-pseudo


-- 
http://annevankesteren.nl/
Received on Thursday, 8 November 2012 09:09:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT