We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The closing the browser panics even if the previous code already panicked and closed the browser.
One of the solutions is to log if we can't close the browser—instead of panic.
As shown in the #814 script, you can see that the current approach (panicking while closing the browser) creates problems.
try
catch
finally
browser.close
The text was updated successfully, but these errors were encountered:
We decided to keep this in the backlog until it becomes necessary to tackle.
Sorry, something went wrong.
No branches or pull requests
The closing the browser panics even if the previous code already panicked and closed the browser.
One of the solutions is to log if we can't close the browser—instead of panic.
As shown in the #814 script, you can see that the current approach (panicking while closing the browser) creates problems.
try
block panics, andcatch
will silence it, and thefinally
closes the browser.browser.close
will cause another panic.The text was updated successfully, but these errors were encountered: