W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2009

[Bug 7411] :invalid and :out-of-range shouldn't match until the user has consciously interacted with the form. Roughly, after the input fires a change event. If, say, <input required> matches :invalid immediately on pageload, it becomes basically useless.

From: <bugzilla@wiggum.w3.org>
Date: Tue, 25 Aug 2009 00:58:01 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MfkML-0006FK-Ub@wiggum.w3.org>

Tab Atkins Jr. <jackalmage@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |jackalmage@gmail.com

--- Comment #1 from Tab Atkins Jr. <jackalmage@gmail.com>  2009-08-25 00:58:01 ---
To be specific, if <input required> matches :invalid immediately on pageload,
then all the warnings an author can specify for invalid inputs (red border,
special background, etc) pop up immediately.  This is generally unacceptable
from a design standpoint - we only want to tell a user they've made a mistake
*after they've actually made a mistake*.

This argument applies generally for anything that can cause an input to match

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 25 August 2009 00:58:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:00:58 UTC