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

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

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

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

--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-11 23:31:47 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: If there are pages that actually break if you implement what the
spec says, then that changes matters. However, I haven't seen any evidence of
this. Pages I looked at that exhibit oninput-like behaviour seem to use
onkeypress, not oninput, since that's what's implemented more widely. (And the
main page I'm thinking of fails to handle paste correctly, which is how I
noticed that it was doing anything like this at all.)

If we don't have a back-compat constraint, then the specced behaviour is
significantly better than requiring UAs to fire oninput after every onkeypress,
because it gives authors a way to do expensive "instant" computation in a way
that doesn't waste CPU resources and in a way that doesn't require complicated
manipulation of timers.

-- 
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 Friday, 11 February 2011 23:31:49 UTC