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

chore: use contentFrame() as a canonical locator representation #32697

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

pavelfeldman
Copy link
Member

No description provided.

This comment has been minimized.

This comment has been minimized.

@@ -82,6 +82,7 @@ If you have a [FrameLocator] object it can be converted to [Locator] pointing to


## method: FrameLocator.first
* deprecated: You should use [`method: Locator.first`] followed by [`method: Locator.contentFrame`] instead.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Use ... instead. ?

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

Test results for "tests 1"

3 failed
❌ [chromium-library] › library/client-certificates.spec.ts:237:3 › fetch › should fail with matching certificates in legacy pfx format
❌ [chromium-library] › library/client-certificates.spec.ts:602:3 › browser › should fail with matching certificates in legacy pfx format
❌ [playwright-test] › babel.spec.ts:135:5 › should not transform external

1 flaky ⚠️ [webkit-library] › library/download.spec.ts:698:3 › should convert navigation to a resource with unsupported mime type into download

35508 passed, 659 skipped
✔️✔️✔️

Merge workflow run.

@pavelfeldman pavelfeldman merged commit 2f4acbb into microsoft:main Sep 19, 2024
28 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants