Make innerText locator work with non-element nodes

[OrKoN]

This PR changes the innerText locator to handle non-Element nodes correctly.

---

Preview | Diff

[sadym-chromium]

@OrKoN do we have any blockers for this PR?

[OrKoN]

@sadym-chromium Mozilla's review I believe

[sadym-chromium]

There is still an open question how to deal with request with document as a start node, and maxDepth equals zero:

{
    "type": "innerText",
    "maxDepth": 0,
    "value": "BAR"
}

As long as document does not have innerText, we can:

1. Traverse to the nearest child html element(s) and perform search there
2. Return an empty array.
3. Do not decrease maxDepth on non-html elements.

@OrKoN @jgraham

[OrKoN]

@sadym-chromium I think #2 would be something I would expect. I.e., the document does match and the max depth is 0, therefore, no recursive calls.

[sadym-chromium]

@sadym-chromium I think #2 would be something I would expect. I.e., the document does match and the max depth is 0, therefore, no recursive calls.

Currently spec says in this case the search should go to all the depth.

[sadym-chromium]

Option 2: web-platform-tests/wpt#46346
Option 3: web-platform-tests/wpt#46345

[jgraham]

I feel like users are probably going to expect not decreasing depth on document elements i.e. passing in document is equivalent to document.documentElement, but we should at least be consistent between different selector types. That would also be inconsistent with the way that node serialization works, but maybe that is less important?

[whimboo]

@OrKoN are you going to create / update wpt tests for this change?

[sadym-chromium]

I feel like users are probably going to expect not decreasing depth on document elements i.e. passing in document is equivalent to document.documentElement, but we should at least be consistent between different selector types. That would also be inconsistent with the way that node serialization works, but maybe that is less important?

Here is the spec change for this option: #713

[OrKoN]

@whimboo @sadym-chromium will update it after the remaining issue is resolved

[sadym-chromium]

• Spec: Update browsingContext.locateNodes #713
• WPT: [WebDriver] align locate_nodes/locator.py with spec web-platform-tests/wpt#46345