History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SEL-498
Type: Bug Bug
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Haw-Bin Chai
Reporter: Dennis Kieselhorst
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Selenium

XPath parse error

Created: 31/Oct/07 02:56 AM   Updated: 27/Feb/08 09:17 PM
Component/s: XPath
Affects Version/s: 0.8.3
Fix Version/s: 1.0

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Windows XP, IE6


 Description  « Hide
com.thoughtworks.selenium.SeleniumException: ERROR: Selenium failure. Please report to the Selenium Users forum at http://forums.openqa.org, with error details from the log window. The error message is: XPath parse error //img[@_actionId='FAST_CREATE'][1]:
//
Step
[
@
at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:73)
at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:82)


[INFO] 08:44:49,265 INFO [org.openqa.selenium.server.SeleniumDriverResourceHandler] Command request: click[xpath=//img[@_actionId
='FAST_CREATE'][1], ] on session 680750
[INFO] 08:44:49,390 INFO [org.openqa.selenium.server.SeleniumDriverResourceHandler] Got result: ERROR: Selenium failure. Please r
eport to the Selenium Users forum at http://forums.openqa.org, with error details from the log window. The error message is: XPat
h parse error //img[@_actionId='FAST_CREATE'][1]:
[INFO] //
[INFO] Step
[INFO] [
[INFO] @ on session 680750

 All   Comments   Work Log   Change History      Sort Order:
Haw-Bin Chai - 27/Feb/08 09:07 PM
It appears the issue is with the first character in the attribute step being the underscore (ajaxslt engine only; Firefox native engine seems fine). Removing the underscore causes the issue to go away.

Haw-Bin Chai - 27/Feb/08 09:17 PM
I originally reproduced the issue using the IDE with a slightly older version of Core. Updating to the more recent snapshot, the issue has gone away, probably due to some ajaxslt fixes. So I don't deserve the credit here. :)