Speed up waitForToastMessageGone, handle error case #5489
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge #5488 first
While working on the tryForTime change, I happened across another random functional test failure. Leadfoot's
findAllByCssSelector
apparently can either resolve with an empty array or reject, and there's seemingly no simple way to check for which will happen.catch
handler towaitForToastMessageGone
waitForToastMessageGone