fix: seeAttributesOnElements check condition - #4029
Merged
Merged
Conversation
Arhell
approved these changes
Nov 30, 2023
|
@kobenguyent With this update we are seeing issue when we use any solution ? |
Collaborator
Author
|
@basalingayyakaramadi please give us a sample code to reproduce your issue |
|
Eg: i will setup actual code and let you know. |
You are correct, reason being Playwright returns non-value attributes as booleans and this mr started using .includes which is string method. Change also makes attribute selectors essentially wildcards as any substring match will pass. Which is something likely not wanted. Therefore href should be handled separately from others. |
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.
Motivation/Description of the PR
Applicable helpers:
Type of change
Checklist:
npm run docs)npm run lint)npm test)