Get-SeElement : A single element was expected but 2 elements were found using the locator TagName with value submit. #186
Comments
itfranck
added a commit
that referenced
this issue
Dec 5, 2020
… ) Also fixed a logic error with $Value that was used both as a parameter and a variable, which caused issues.
Merged
itfranck
added a commit
that referenced
this issue
Dec 6, 2020
* Start-SeEdgeDriver throw error on launch (#188) * Edge fix + general debug fix * .Where is not a method for CIM Instance object (#190) * Firefox not using the proper DriverOption (#191) * Filter parameter to get-seelement and applied to Get-SeInput (#186 #192 ) Also fixed a logic error with $Value that was used both as a parameter and a variable, which caused issues. * Legacy code removal causing error with screenshots (#187) * Fix - Filter + Filter error message * Select input by attributes fix. * Edge (new) driver option need to be of type ChromeOptions (#195) * Edge driver option fix (#193) * Edge - semi revert (#197) Since Start-SeDriver have priority over options, options should not handle stuff that depends on parameters. * IE fix (#193) * MSEdge Fix (#193) * ErrorAction Stop when MSEdge Service fail to create. * AcceptInsecureCertificates (Firefox, Chrome, Edge) (#189) * #177 Get-SeInput view (initial commit) * V4.0.0-preview2 build * Drivers update * V4.0.0-preview2 changelog * Version update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Found that on company site (Office 365)
Get-SeInput -Type email -Single give an error :
Get-SeElement : A single element was expected but 2 elements were found using the locator TagName with value submit.
(There is only one correpsonding email field so error should not be thrown)
I will investigate and address by tomorrow EOD
The text was updated successfully, but these errors were encountered: