This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-input-element Comment: spec input.onsearch and I will ensure that your comment is descriptive enough that the editor can understand it. Posted from: 80.200.76.108 by ms2ger@gmail.com
At least github relies on it.
Can't we advice them to use oninput instead? It just makes no sense whatsoever.
I don't understand the reason for this feature either.
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: Did Not Understand Request Change Description: no spec change Rationale: The comment is not descriptive enough for the editor to understand it. What are you asking for here? What is input.onsearch? What does it do that input.oninput doesn't do? Who supports it?