Repository navigation
feat: support locating element inside an iframe - #2
Merged
Merged
Conversation
sheremet-va
requested changes
Jun 3, 2025
sheremet-va
left a comment
Member
There was a problem hiding this comment.
Looks good to me, but can you add a test?
Member
It's not a vitest thing, iframes are loaded asynchronously, you can use |
Contributor
Author
Added a test with the |
sheremet-va
reviewed
Jun 4, 2025
sheremet-va
approved these changes
Jun 4, 2025
Member
|
Released in 1.7.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to vitest-dev/vitest#6966 and vitest-dev/vitest#8016.
Retrieves the iframe's
contentDocumentwhen querying locator.contentDocumentis only available onsame-originurls.I noticed that on the vitest test, the iframe doesn't load Immediately.
expect.elementworks. Not sure if there is a way to prevent this?