Revisit Get-SeElement wait condition.

[itfranck]

We used PresenceofAllElementLocatedBy when using a timeout, which might not wait long enough.

I think we should probably use ElementIsVisible (unlessAll switch is used, in which case ElementExists) and then potentially make a second call to get the actual elements.

Otherwise we end up needing to do :

Start-SeDriver -Browser Chrome -Position 1920x0 -StartURL 'https://login.live.com/login.srf' -ImplicitWait 10 # Implicit wait didn't change anything here
 Wait-SeElement -By TagName -Value input -Condition ElementIsVisible -Timeout 10
$EmailField =  Get-SeInput -Type email -Timeout 3
$EmailField | Invoke-SeKeys -Keys 'itfranck@example.com'

I think the Wait-SeElement part should not be required everywhere and intrinsic to the process.
Ultimately, using this module should be as smooth as using the browser.

[franklin050187]

Hello,

I would like to +1 this request :
adding a -visible switch and -clickable switch would greatly help smoothness of test instead of using what @itfranck is doing or what I do (add start-sleep -seconds 1 because I know every action on a specific website has a fading frame of .8 sec after every click)

from https://www.selenium.dev/documentation/fr/webdriver/waits/
new WebDriverWait(driver, TimeSpan.FromSeconds(3)).Until(ExpectedConditions.ElementToBeClickable(By.XPath("//a/h3")));
maybe having a passthrough here could be a starting point