-
Notifications
You must be signed in to change notification settings - Fork 5
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
element.querySelectorAll returns 0 elements in some cases #206
Comments
niklasHagner
changed the title
querySelectorAll returns 0 elements incorrectly
element.querySelectorAll returns 0 elements in some cases
Apr 17, 2024
PS: Was using tallahassee v14.5.0 So might be an obsolete issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is not a well defined issue, I figured I'd post it first with my initial findings and not spend extra time creating an isolated test-case - because I'm not sure what the intended support for
querySelectorAll
is supposed to be in Tallahassee these days.I just discovered this:
I was working in test with mocha + tallahaassee.
browser.document.querySelectorAll(".bylines .watch--follow")
- this worked fine and it did find one matching elementarticleElement.querySelector(".bylines .watch--follow").innerHTML
- that also worked finearticleElement.querySelectorAll(".bylines .watch--follow").length
I got the output0
Screenshot from my vsCode debug console, while debugging a test
.querySelector(".bylines .watch--follow").innerHTML
- this finds an element and outputs some html.querySelectorAll(".bylines .watch--follow").length
this finds zero elementsI'm suspecting that
browser.document.querySelectorAll
works fine butelement.querySelectorAll
does not.Is this perhaps an expected limitation of the tallahaassee support for
querySelectorAll
?The text was updated successfully, but these errors were encountered: