Rule Proposal: no-disabled-button

[beefancohen]

based on this article: https://axesslab.com/disabled-buttons-suck/
wanted to hear people's thoughts on this!

tldr; disabled buttons provide low-contrast non-interactive experiences. in the author's opinion, it is a better UX for both abled and disabled users to enable all buttons and provide clear error messaging when clicked if the user cannot perform the intended action.

Can also add into logic and/or option for proposed button-is-valid #186

[ljharb]

The author makes good points, but I don't agree that the suggestion would be an improvement. It sounds like better styling would solve most of the issues; if a button is enabled but shows an alert or similar, there's no declarative way to identify beforehand that the button is semantically disabled.

I think at the least it should be a separate rule; the airbnb config wouldn't ever enable it; and in general I don't think it's a good rule to exist.

[ljharb]

Rule about the type added to eslint-plugin-react in jsx-eslint/eslint-plugin-react#1525