From 8c1ffaf0acc28f22e30b82624dc6c07887dd0ba7 Mon Sep 17 00:00:00 2001 From: Allan Loh Date: Mon, 9 May 2016 09:00:13 +0800 Subject: [PATCH] Update docs for accessing underlying WebElement The old documentation had an example that didn't compile for accessing the underlying IWebElement. var webElement = element() as OpenQA.Selenium.IWebElement; Have updated to reflect a way that has worked for me to get the underlying element. --- Docs/v3/actions.find.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Docs/v3/actions.find.md b/Docs/v3/actions.find.md index 2bdd2bc..8c9170d 100644 --- a/Docs/v3/actions.find.md +++ b/Docs/v3/actions.find.md @@ -15,14 +15,14 @@ Often this function is used to break through the abstraction and get direct acce var element = I.Find("#searchBox"); // Get reference to underlying IWebElement (Selenium) -var webElement = element() as OpenQA.Selenium.IWebElement; +var webElement = (element.Element as Element)?.WebElement as OpenQA.Selenium.IWebElement; // Get reference to underlying WatiN.Core.Element (WatiN) -var webElement = element() as WatiN.Core.Element; +var webElement = (element.Element as Element)?.WebElement as WatiN.Core.Element; // Find a collection of elements matching selector var listItems = I.FindMultiple("li"); ``` ```vbnet // TODO - Visual Basic Code Sample -``` \ No newline at end of file +```