3

Why XPath does not highlight the yellow mark? I try to find the XPath at www.google.com

//*[@id="fakebox-input"]

It is found but not highlighted being the yellow mark on Chrome so it's hard for me to found out exactly where is the XPath and to see the XPath correct or not.

Is there a solution to this issue?

DebanjanB
  • 118,661
  • 30
  • 168
  • 217
daptyo
  • 51
  • 3
  • You've still not created a [mcve]. Your question should stand on its own, not be dependent upon a link that can change in the future or change depending on the viewer. (For example, that XPath returns an empty array for me at that site at this moment in time and with my current set of extensions. Evaluating this expression, `$x('//@id').map(x => x.value)`, in the console returns a list of 43 id values, none of which are `fakebox-input`.) Post a self-contained example in your question if you want further help. – kjhughes Jul 17 '20 at 03:22
  • 1
    recent update of Chrome 84 is buggy you can find more details on https://stackoverflow.com/a/62972580/5400362. – Dev Jul 18 '20 at 19:15

2 Answers2

4

Here the major issue is with DevTools within Google Chrome 84.0 which doesn't highlights the first matched element.

Incase, the locator finds a single match, the search result does show 1 of 1 but the WebElement is not highlighted within the DOM Tree

As an example, the Search Box within the Google Home Page can be identified uniquely using the :

[name='q']

or using the :

//*[@name='q']

But within Google Chrome 84.0, does finds the element and shows 1 of 1 but the element is not highlighted.

devtools_issue

However, if there are multiple element matching to the Locator Strategy, leaving out the first matched element, the other elements are highlighted.

Bug in Chrome v84.0.4147.89

This issue was raised in the Platform>DevTools queue through Issue 1108311: The first matched element in the Elements panel is not getting highlighted as per the cssSelector and had been merged into Issue 1103316: Elements search does not resolveNode (highlight text, etc) on first search result where we are actively tracking the issue.

Solution

As per @bugdroid the main issue was caused because a check to ensure the search results were valid did not account for the case where the index was 0, so all highlight results of index 0 (index 1 to the user) were no longer highlighted.

The fix for this issue is Merge-Approved in:

Alternate Strategies

You have two(2) other approaches as solutions as follows:

  • In the first approach, as per the article Fix site issues with the new Issues tab you can use the command document.querySelector() through the newly added Console tab within the second Drawer from the top to query the element through the css-selector as follows:

query_selector_css

  • In the other approach, you can click on the Console tab, next to Element tab and execute the either of the following xpath/css commands:

    • command as:

      $x("//*[@name='q']")

    • Snapshot of identification:

console_tab_xpath

  • command as:

    $$("[name='q']")

  • Snapshot of identification:

console_tab_css-selector

DebanjanB
  • 118,661
  • 30
  • 168
  • 217
2

The bounty belongs to @DebanjanB however to add a quick note that they've now fixed this in at least Version 84.0.4147.105 (Official Build) (64-bit).

Just go to chrome://settings/help an let chrome update.

This is this page, working for a single highlight devtools working

DebanjanB
  • 118,661
  • 30
  • 168
  • 217
RichEdwards
  • 2,205
  • 2
  • 2
  • 15
  • 1
    It's a minor push and doesn't needs user intervention. So explicitly browsing to chrome://settings/help may not be required as the minor pushes are automatic. – DebanjanB Jul 31 '20 at 08:14