By.XPath broken in latest

[richard-browne]

I just updated to SimpleBrowser.0.5.45.0 & SimpleBrowser.WebDriver.0.5.30. Now By.XPath is broken. Example:

    {
        var by = By.XPath("//input[contains(@id, 'foo')]");
        return browser.FindElement(by);
    }

Exception:

System.ArgumentNullException : Value cannot be null.
Parameter name: node

at System.Xml.XPath.Extensions.XPathSelectElements(XNode node, String expression, IXmlNamespaceResolver resolver)
at SimpleBrowser.WebDriver.WebElement.FindElementsByXPath(String xpath)
at SimpleBrowser.WebDriver.WebElement.FindElementByXPath(String xpath)
at OpenQA.Selenium.By.<>c__DisplayClasse.b__c(ISearchContext context)
at OpenQA.Selenium.By.FindElement(ISearchContext context)
at SimpleBrowser.WebDriver.SimpleBrowserDriver.FindElement(By by)

[Teun]

Owch. On all documents or something specific? Can you provide a full
breaking example?

2014-07-03 9:57 GMT+02:00 richard-browne notifications@github.com:

I just updated to SimpleBrowser.0.5.45.0 & SimpleBrowser.WebDriver.0.5.30.
Now By.XPath is broken. Example:

{
    var by = By.XPath("//input[contains(@id, 'foo')]");
    return browser.FindElement(by);
}

Exception:

System.ArgumentNullException : Value cannot be null.
Parameter name: node

at System.Xml.XPath.Extensions.XPathSelectElements(XNode node, String
expression, IXmlNamespaceResolver resolver)
at SimpleBrowser.WebDriver.WebElement.FindElementsByXPath(String xpath)
at SimpleBrowser.WebDriver.WebElement.FindElementByXPath(String xpath)
at OpenQA.Selenium.By.<>c__DisplayClasse.b__c(ISearchContext context)
at OpenQA.Selenium.By.FindElement(ISearchContext context)
at SimpleBrowser.WebDriver.SimpleBrowserDriver.FindElement(By by)

—
Reply to this email directly or view it on GitHub
#24.

[Teun]

I just looked into this and could easily reproduce. Sorry that I left it so long. Will fix.

[Teun]

It's fixed and pushed to nuget. Sorry that I didn't take the report more seriously when submitted.

[richard-browne]

No probs. Thanks for fixing.

On 28 Aug 2014, at 1:28 am, Teun notifications@github.com wrote:

It's fixed and pushed to nuget. Sorry that I didn't take the report more seriously when submitted.

—
Reply to this email directly or view it on GitHub.