-
Notifications
You must be signed in to change notification settings - Fork 21
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
(DomActions) WTR tests for elementSelector() #495
(DomActions) WTR tests for elementSelector() #495
Conversation
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.
This is great @freiondrej! I just had a couple minor remarks. Thank you for doing this!
]) | ||
}) | ||
}) | ||
describe('querySelectorChain', () => { |
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.
could you add a test for Shadow DOM? something for ['.my-shadow-root-selector', '.selector-inside-shadow-root']
?
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.
good call! I'll adjust the should return elements by querySelectorAll from shadow root if available
which now cannot be used directly anymore as the elementSelector() only accepts one argument.
@freiondrej do you want to follow up here? |
Yes, absolutely :) I just didn't have a free evening yet, apologies. |
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.
LGTM!
Hey @muodov, will it bring value to continue covering DomActions like this? I can try to send a PR every now and then :) or pls point me to some higher-value task 🙏