- From: <bugzilla@jessica.w3.org>
- Date: Sat, 01 Jan 2011 06:10:58 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-01 06:10:57 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: Since you can't register capturing handlers declaratively, and since
form controls can be all over the place in the DOM now, I think 'forminput' and
'formchange' are still very helpful and have clear use cases. As as
straightforward demonstration of this, try to rewrite the examples in the spec
that use these features to do them without onforminput/onformchange and see
whether it's still as simple.
--
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 Saturday, 1 January 2011 06:10:59 UTC