selene
selene copied to clipboard
consider adding config.click_by_js
You might ask, why didn't we have config.click_by_js till now?
Because making all clicks js based is not a "normal case".
You might need to speed up all "set value" in your tests, but command.js.click will not speed up anything.
Yet, sometimes, it might be useful as workaround.
In such cases - it was considered a good practice to use
element.perform(command.js.click)
to achieve the goal in less concise way,
thus, identifying by this "awkwardness" that it is really a workaround;)
Yet, the latter was pretty subjective... And one would like to hide such awkwardness via element.with_(click_by_js=True), so when we call element.click - it looks nicer :)
Hence.... Ok) let's add it)