Improving "wait for element" command

[YecineM]

🚀 Feature Proposal

I propose that some generous people develop: a modified version of the command "wait for element visible" that doesn't cause termination of the test when it fails.

Motivation

It would be very helpful, because my test would continue after the timeout has elapsed.

Example

In a loop.

[YecineM]

@toddtarsi Could you include that in the version 4 please ?

[toddtarsi]

@YecineM - I don't think I can fully disable this being a failure, as that may break other people's tests. I'll look around though. I think we may have something available to do this possibly in the control flow system.

[YecineM]

Oh my god, thank you, that would be so beneficial in my work.

For some reason or bug, the "web element" I'm dealing with doesn't show up if the wait time is too long (an hour or more). So I need to make a Selenium IDE test that reloads the page and repeats the wait command every 30 minutes, for example.

[YecineM]

I'm counting on you, dear developers <3

[toddtarsi]

@YecineM - The PR is a work in progress here, but there are a number of things that have to happen first. Basically, this needs to clear alpha before January, when v3 gets taken down from the stores, so it might be a while. I'm sorry for the delays, but we're at least working our way through various stabilizations.