- From: <bugzilla@jessica.w3.org>
- Date: Sun, 26 Sep 2010 02:29:17 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10552
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WORKSFORME
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-26 02:29:17 ---
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: The spec already says "When the input event applies, any time the
user causes the element's value to change, the user agent must queue a task to
fire a simple event that bubbles named input at the input element", and similar
text for 'change', so it seems clear to me that such UI should fire the
relevant events accordingly.
In the case of the field clearing button, it should fire "oninput", but I don't
think it should fire "onchange" until the control loses focus, by the way.
--
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 Sunday, 26 September 2010 02:29:19 UTC