W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11253] Description of input event doesn't seem to match what browsers do

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Jan 2011 20:20:45 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pckhx-0000xr-RR@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11253

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #4 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-01-11 20:20:44 UTC ---
Maybe, but the fact still remains that the behavior described in the spec is
not actually implemented by any browser AFAICT, so it's still misleading.  It
would be more helpful to say that browsers should fire the event on every
character if the user is inputting one character at a time, but may also fire
one event for multiple characters as well (e.g., in the examples you just
gave).

It's true that a script that expects input events on every keypress is already
broken, but there's a big difference between broken in edge cases like
copy-paste and broken for users typing normally on a keyboard.  It's entirely
possible that there are many pages that rely on browsers not doing what the
spec describes, even though occasionally it fails, and in that case any new
browser would have to match existing browsers' behavior for compat.  Thus it
should be specced.

-- 
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, 11 January 2011 20:20:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 20:20:47 GMT