21265 2013-03-13 13:08:15 +0000 Be more strict/clear for 'explicit commit action' for the change event 2016-04-21 22:29:12 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED FIXED P2 editorial --- 1 alexander.farkas robin mike public-html-admin public-html-wg-issue-tracking robin travil public-html-bugzilla oldest_to_newest 84332 0 alexander.farkas 2013-03-13 13:08:15 +0000 The bug explains the explicit commit action with two examples. (see: http://www.w3.org/TR/html5/forms.html#event-input-change) In the second example it says: "... a Date control that allows both text-based user input and user selection from a drop-down calendar: while text input might not have an explicit commit step, ..." I think the "might" should be changed to either "should" or "must". i.e.: "... a Date control that allows both text-based user input and user selection from a drop-down calendar: while text input *must* not have an explicit commit step, ..." It would be also great to explain an explicit commit action in case of an input[type="range"]. Because both current examples involve a "popover menu" (file select, date calendar). While a range has a totally different UI. For example, while the user holds the mouse and is dragging, he hasn't commited a change (only input event occurs). As soon as the user releases his mouse button (mousup, touchend, keyup etc.), he has commited a change. 126028 1 travil 2016-04-21 21:37:47 +0000 Looking at: https://jsfiddle.net/a5hsz3j6/ to see how this works in browsers today... 126037 2 travil 2016-04-21 22:29:12 +0000 HTML5.1 Bugzilla Bug Triage: I believe I've given this a shot at commit: https://github.com/travisleithead/html/commit/2e4e670f04a938686fc0703bf54d4b9ebf8ccee6 I also added a third example. Apologies that this commit also has a trailing whitespace cleanup as well. Your changes are only around the relevant spec text not spread out anywhere else... (This PR is not yet merged; comments welcome.) If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!