This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the spec for the new search input type, it is said : "The difference between the Text state and the Search state is primarily stylistic: on platforms where search fields are distinguished from regular text fields, the Search state might result in an appearance consistent with the platform's search fields rather than appearing like a regular text field." And : "The input and change events apply." I suppose it should be specified too that whatever platform search field action is implemented should trigger the change events. I think it is an issue because of the chromium implementation of input type search : A cross is drawed that let empty the input value on click, but it does not fire the onChange event. The problem may be the mention that the difference is "primarily stylistic". It sounds like it can be "secondarily functional", but give no indications about that.
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.