-
Notifications
You must be signed in to change notification settings - Fork 32
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
Using *
as locator returns no nodes
#2539
Comments
@sadym-chromium PTAL |
e2e repro works: #2543. Looking further |
UPD: the issue should be fixed by #2543 |
The root cause is in the fact Chromium BiDi used |
Addressing #2539 According to the spec, the default `startNodes` of the `browsingContext.locateNodes` is `document`, not `document.body`.
Thanks for fixing this. @sadym-chromium why would it still return no nodes given the selector |
In your example the page is "about:blank", and there are no elements in the "document.body" |
…2543) Addressing GoogleChromeLabs#2539 According to the spec, the default `startNodes` of the `browsingContext.locateNodes` is `document`, not `document.body`.
This behavior is observed in
stable
andcanary
(130.0.6682.2)Expected Behavior
If I call
browsingContext.locateNodes
with the following parameters:I would expect that it would fetch the ` tag as it is the first element in the DOM tree.
Actual Behavior
Firefox: ✅ works as expected and returns
Chrome: ❌ fails even though
*
is a valid selector and returnsReproducible Example
See https://github.com/christian-bromann/bidi-locateNodes-error, clone the repo, install dependencies, and call
npm run wdio
The text was updated successfully, but these errors were encountered: