[Enhancement] Support "suppressNotFoundErrors" option for "waitFor..." commands

[benjaminr-ps]

Is your feature request related to a problem? Please describe.
I want to wait for an element beeing present after some time, to be optional only and not failing.
The use case for instance is loading spinner, which blocks any interaction.
The loading spinner may vary in its presence, which might be due to the backend systems.
To circumvent that fact, I use the waitForElementPresent command.
But if the element is not found by selector (of any kind) the command let the test fail.

Describe the solution you'd like
The waitFor commands (or especially the waitForElementPresent command) should allow to define a flag to suppress this not founding.

Describe how the solution will work
In the Page Object's elements selection, the "suppressNotFoundErrors" can be defined optionally.
Whenever this is defined and set to "true", the waitFor command will silently fail and does not propagate higher.

Describe alternatives you've considered
Add a further parameter to the waitFor commands, depicted to suppressNotFoundErrors.

Additional context
Nothing

[Pieras2]

If I well understand, do you want a command that waits for an element that will appear in future?
If so, it can be solved by preparing your own custom command using available api cmds

[benjaminr-ps]

@Pieras2 No, this capability already exists by the waitForElementPresent(/Visible) command.

I would like to have the ability to suppress the "element was not found error", which might occur, if element does not show up in future.

This kind of behaviour was already implemented for other element commands, like getText or getAttribute.

[Dharin-shah]

PR for the same
#2632

[beatfactor]

I'm afraid this is not how the suppressNotFoundErrors flag is supposed to work and it cannot be added for waitFor commands. Commands like waitForElementVisible already suppress the notFound errors and the assertion should always fail if the element is not found.

This flag is only useful for assertions like assert.visible where the element might not exist and only to avoid the additional errors in the output. waitForElementVisible is supposed to be the same as assert.visible with suppressNotFoundErrors: true.