Don't fire input event for radio buttons or checkboxes

[zcorpan]

From web-platform-tests/wpt#2539

Tests:
radio button http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3859
checkbox http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3860

It seems Chromium/WebKit/Gecko don't fire input event. (Note that "input 1" does not appear in the log.) Haven't tested Edge.

cc @cvrebert

[zcorpan]

(Should probably test all input types to get a bigger picture.)

[cvrebert]

See the Notes (and bugs linked therein) of http://caniuse.com/#feat=input-event

To be clear, the currently-spec'd behavior of input is sensible and I like it personally.

[cvrebert]

To summarize:

Fires input events?	<select>	<input type="checkbox"> & <input type="radio">	<input type="file">
Chrome	✅ Yes	❌ No: https://crbug.com/534245	❌ No: https://crbug.com/534245
Safari	✅ Yes	❌ No: http://webkit.org/b/149398	❌ No: http://webkit.org/b/149398
Firefox	❌ No: http://bugzil.la/1024350	❌ No: http://bugzil.la/1206616	❌ No: http://bugzil.la/1206616
Edge	❌ No: bug 1816207	❌ No: bug 1883692 & UserVoice 10182111	✅ Yes
IE11	❌ No	❌ No	Probably Yes

[zcorpan]

Thank you for the summary and the links! Very helpful!

[cvrebert]

@zcorpan So what's the next step here?

[zcorpan]

I think we should leave the spec as is and hope browsers implement input events everywhere. In a year or two we can revisit this if browsers still haven't implemented.

Next step is probably to cc someone who could fix the bug for each bug. I can do that for Chromium.

[annevk]

@miketaylr @RByers some of the above may exhibit itself as webcompat issues. ^^

[miketaylr]

Thanks @annevk. I haven't found any yet, but this Gecko bug feels related: events fired on <option> don't bubble up to <select> https://bugzilla.mozilla.org/show_bug.cgi?id=1090602 (which we WONTFIX'd because platform/browser behavior is all over the place. See comment 27 and 34 and then test multi/inline select and weep because it gets more inconsistent).

[RByers]

@annevk, thanks. My team is working on input events, so I've added this bug to our TODO list. Do let me know if a webcompat issue surfaces in practice and we can bump the priority.