XPath: window is highlighted in red, Invalid XPath or No matching nodes error, and no HTML in console window

312 views
Skip to first unread message

B Lee

unread,
Dec 3, 2014, 6:48:13 PM12/3/14
to fir...@googlegroups.com
Firebug version: 2.0.6b1
Browser version: Firefox 34.0
Operating system: Windows 7

Recently my Firefox was automatically upgraded from 33 to 34.0 and since then, there have been problems when using the FirePath tool in that:

1. The XPath: value, while still showing, is highlighted in red in the text window.
2. The status bar will show either "No matching nodes" or "Invalid XPath" depending on what was selected.
3. In the Console window underneath the FirePath tab, the HTML code no longer appears.

Steps to Reproduce:

1. On Windows 7 with Firefox 34.0 go to www.cnn.com.
2. Press the Firebug button on the main menu to open Firebug.
3. In the Firebug window, click on the FirePath tab.
4. Press the Inspect Element button on the Firebug menu, second to the left.
5. Click on one of the links on the page, such as Politics.

Actual Result:
The XPath: is highlighted in red, the Invalid XPath message appears, and no HTML code appears in the Console section other than a <document>.
Screenshot is attached.

I've selected the Reset All Firebug Options several times to no avail.

Expected Result:
Previously for Firefox 33, when using Firebug the FirePath worked properly with no red highlight, no error message, and the HTML code appeared immediately after selecting an element by XPath.
xpath_error.png

Sebastian Zartner

unread,
Dec 4, 2014, 4:07:18 AM12/4/14
to fir...@googlegroups.com
Thank you for the detailed description. Though note that FirePath is not maintained by the Firebug Working Group.
This problem is already filed against the FirePath issue tracker. So you may follow that issue.

Also note that you can also test XPaths using Firebug's $x() command.

Sebastian

B Lee

unread,
Dec 8, 2014, 12:31:41 PM12/8/14
to fir...@googlegroups.com
Thanks for your response. It's been reported on FirePath and it's just been fixed.
Reply all
Reply to author
Forward
0 new messages