Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supress error for chained .find() command #4079

Open
dikwickley opened this issue Mar 1, 2024 · 1 comment · May be fixed by #4100 or #4119
Open

Supress error for chained .find() command #4079

dikwickley opened this issue Mar 1, 2024 · 1 comment · May be fixed by #4100 or #4119

Comments

@dikwickley
Copy link
Contributor

Description of the bug/issue

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).

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

@ScraperWizard
Copy link

ScraperWizard commented Mar 2, 2024

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?

@dikwickley dikwickley linked a pull request Mar 12, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants