You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use jsdom to traverse nodes and generate XPath. The algorithm is consistent with the browser's method of obtaining XPath. However, I've found that jsdom behaves differently from the browser in some ways, leading to discrepancies between the XPath generated by jsdom and that obtained by the browser.
Output: hrp-button hrp-button_option, The actual correct output should be a3.
The text was updated successfully, but these errors were encountered:
Basic info:
I use jsdom to traverse nodes and generate XPath. The algorithm is consistent with the browser's method of obtaining XPath. However, I've found that jsdom behaves differently from the browser in some ways, leading to discrepancies between the XPath generated by jsdom and that obtained by the browser.
Output: hrp-button hrp-button_option, The actual correct output should be a3.
The text was updated successfully, but these errors were encountered: