W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2013

[Bug 22070] New: Revive textInput in DOM3

From: <bugzilla@jessica.w3.org>
Date: Fri, 17 May 2013 15:58:43 +0000
To: www-dom@w3.org
Message-ID: <bug-22070-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22070

            Bug ID: 22070
           Summary: Revive textInput in DOM3
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: garykac@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

textInput (the replacement for keypress) was removed from the spec because
it was thought that the more general 'input' event would be a suitable
replacement. However, this is not the case.

'input' is not a valid replacement because:
* it fires after the chars have been added to the field (ie: you can't cancel
the key)
* it doesn't indicate what new chars were added (only that something changed)

'beforeinput' is slightly better, but still not appropriate:
* it doesn't indicate what new chars were added (only that something changed)

Without something like textInput, browsers will still be forced to support
keypress because we will not be providing replacement functionality. Either
that
or developers would need to manually track the contents of each field and
compare
to see what had changed between each event (ugh!).

We need to:
1) Reinstate textInput
2) Remove all references to HTML5 'input' as a replacement for keypress

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 17 May 2013 15:58:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:20 UTC