-
Notifications
You must be signed in to change notification settings - Fork 42
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
Fix isVisible #1108
Fix isVisible #1108
Conversation
b0a3d61
to
c368543
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Some suggestions.
@ankur22 Does this conform to auto-waiting actionability checks? https://playwright.dev/docs/actionability
No, this isn't a prerequisite for the |
c368543
to
9e1d3ed
Compare
d7f3f53
to
a9cb198
Compare
9e1d3ed
to
b971314
Compare
b971314
to
be914dc
Compare
This method is to be used when an API needs to: 1. query for a handler given a selector with or without strict mode enabled. 2. Perform an action on the handler if one was found, otherwise return false. 3. Not wait for the element that matches the given selector. This will make the timeout option obsolete on APIs that work with this.
isVisible is changed to work with the new runActionOnSelector method, which does not wait for any elements to match the given selector. It will just return false if there are no matching elements. This also means that timeout is an obsolete option, which means that the test in locator_test is not valid and has been removed.
be914dc
to
317efca
Compare
What?
This fixes
isVisible
so that it does not wait for an element to match with the given selector, and returns straight away. This makes thetimeout
option obsolete.Why?
There are two reason to make this change:
Checklist
Related PR(s)/Issue(s)
Updates: #981