Clicking on disabled elements (buttons) should fail the same way as clicking on covered ones

[angryziber]

The problem

Flaky test because of Selenide clicking disabled element and not failing.

Details

In our project, from time to time running post requests disable all submit buttons and then clicking those by Selenide just has no effect, making the test fail later on, which is harder to diagnose.

We propose failing the test if trying to click a disabled button (after the usual timeout of course).
There are no legitimate use cases of actually clicking disabled buttons, because it has no effect by design.
If somebody wants to check if the button is disabled or not, they can just use shouldBe(disabled)

Tell us about your environment

selenide:6.13.1

[jazzboy65]

Maybe we are talking about different things, but what happens in your attributes? had a similar case and helped shouldBe(Condition.atrribute(as Example "aria-disabled","true"))

[asolntsev]

@jazzboy65 No, the point is that $.click() should check that the element is enabled.
Currently $.click() only checks that the element is visible.