fix(testing): re-add Puppeteer asElement()
calls
#5114
Merged
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.
What is the current behavior?
Fixes a regression caused by the removal of a few
asElement()
calls in 91cfa2c. Turns out these are necessary for the case where the handle isnull
. To avoid type errors, we cast the returned value to be of typeElementHandle<Element>
rather thanElementHandle<Node
.Fixes: #5113
What is the new behavior?
No more errors 🙂
Does this introduce a breaking change?
Testing
npm run test
and observe a failure on the second call topage.find
in the e2e testnpm run test
and observe no more errors and tests pass!Other information