You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Further chained .find() commands should not throw the Timeout or any other error again. Ex. in browser.element('.invalid-selector').find('selector').getText();, there should only be one error due to browser.element() and .find() should not throw an error again (suppress the error for it).
I was considering resolving this issue by removing the elements with the same shared parentElement from the queue (Once an error has occurred). Would this approach be effective, or should I look for options to ungracefully exit the function?
Description of the bug/issue
Further chained
.find()
commands should not throw the Timeout or any other error again. Ex. inbrowser.element('.invalid-selector').find('selector').getText();
, there should only be one error due tobrowser.element()
and.find()
should not throw an error again (suppress the error for it).Branched off from issue: #3991
Reference comment: #3991 (comment)
Steps to reproduce
No response
Sample test
No response
Command to run
No response
Verbose Output
No response
Nightwatch Configuration
No response
Nightwatch.js Version
3.3.7
Node Version
No response
Browser
No response
Operating System
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: