[Bug 7411] New: :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.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7411

           Summary: :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.
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://whatwg.org/specs/web-apps/current-work/#matching-
                    html-elements-using-selectors
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Section:
http://whatwg.org/specs/web-apps/current-work/#matching-html-elements-using-selectors

Comment:
: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.

Posted from: 99.35.179.251


-- 
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 Monday, 24 August 2009 21:57:18 UTC