Remove no-onchange from recommended and strict

[karlhorky]

TODO

• Determine which browsers exhibit behavior tested by @diverent2 in Is no-onchange still a relevant rule? #398 (comment)

See #398 (comment)

Closes #398

[ljharb]

Before landing this, I'd like to understand which browsers it's relevant for, so we can note it in the documentation.

[karlhorky]

QuirksMode to the rescue!

When you focus on a select box and go through its options with the keyboard, IE and Opera fire the change event every time you select a new option. The other browsers fire the event only when you confirm the new option by leaving the select box.

So it looks like the bug was there until at least IE10 pr2.

@ljharb does that address the question of compatibility?

https://www.quirksmode.org/dom/events/change.html#t05

[karlhorky]

Also interesting to note is that it was actually written into the DOM spec a long time ago this way: https://bugzilla.mozilla.org/show_bug.cgi?id=969068#c2

[ljharb]

Gotcha, thanks. At the very least, let's add that to the docs - IE 10 is still something many sites have to support, but it's reasonable to take it out of the configs.

[karlhorky]

Ok, I've added a deprecation warning following the other PRs such as #713, along with an explanation. Is it acceptable like this?

I've also marked this PR to close #398 if it gets merged.

[karlhorky]

@ljharb What do you think about my new changes? Is this good to get merged?

[karlhorky]

Thanks for the review and merge @ljharb !