dotnetseleniumtools/dotnetseleniumextras

Extra utilities for use with the Selenium .NET language bindings

DotNetSeleniumExtras

Extra utilities for use with the Selenium .NET language bindings.

This repository is a migration of code from the Selenium project's .NET bindings. It consists of the PageFactory implementation and the ExpectedConditions classes from the Selenium.Support library.

THIS REPOSITORY WILL NOT ACCEPT ISSUES OR PULL REQUESTS UNTIL A NEW OWNER IS FOUND

The code has been extracted here to preserve it for users, to provide a place for users to continue to use the existing implementations when the impelementations are removed from the Selenium project. It is hoped that this repo will serve as a starting point for a community-based implementation of the projects herein, at which point, this repo will no longer be necessary.

dotnetseleniumextras's Issues

Missing License for the Nuget

I'm helping with the project ClearlyDefined which is a database of license information. We are trying to validate the license that applies to this Nuget https://www.nuget.org/packages/DotNetSeleniumExtras.PageObjects/3.11.0.

Can you confirm you published this Nuget and that the Apache-2.0 in this repo applies to this version?

Thanks.

SelectElement is missing in this

When using this new library instead of the Selenium Support to use migrated ExpectedConditions, the SelectElement is missing in this library. I can use both libraries for now, but it is forcing me to work around by explicitly declaring which ExpectedCondition to use. Is there a plan to include SelectElement as well?

Tests are failing

EnvironmentManager is missing files
Missing selenium/common/src/web/ folder
All tests with real browsers are failing.
@jimevans

StalenessOf returns true even if element is attached to the DOM but not enabled

Consider the following line:

DotNetSeleniumExtras/src/WaitHelpers/ExpectedConditions.cs

Line 494 in dc402a5

return element == null || !element.Enabled;

It should not check the actual value of Enabled but only try to access it, since the access itself is what forces the staleness check.

Is this package here to last?

We are evaluating our options to upgrade to Selenium 4 in our company. Since PageFactory is been deprecated now, I came upon this package that could enable us to continue using Page factory elements. I just want to be sure if this package is there to stay before arriving at the decision.

Selenium4 not supporting

When upgraded to Selenium4; it is not supporting DotNetSeleniumExtras

Enhancement Request: Support ISearchContext

IWebDriver and IWebElement are ISearchContext, supporting ISearchContext instead would allow the evaluation of expected condition to be more specific.

SeleniumExtras.WaitHelpers.ExpectedConditions.ElementToBeClickable(IWebelement element) method will encounter a bug if there is a cover layer of loading over the element

Hi, just as title described,It is seems that if there is a cover layer of loading over the element(this element will be enabled and displayed at this time),the ElementToBeClickable method will throw a specified element cannot be clicked exception.

Append the source code about above method:
public static Func<IWebDriver, IWebElement> ElementToBeClickable( IWebElement element) { return (Func<IWebDriver, IWebElement>) (driver => { try { if (element != null && element.Displayed && element.Enabled) return element; return (IWebElement) null; } catch (StaleElementReferenceException ex) { return (IWebElement) null; } }); }

Interesting in taking ownership of this project...

If possible, I'd like to chat a bit about it... please let me know if there is a preferred way of doing this.

Create a Nuget package with references to the WebDriver 4

Hi,

Is it possible to create a new Nuget package with references to the Selenium WebDriver 4 ? They change the location of IWrapElement (not in Internal anymore) and using the current installed DotNetSeleniumExtras doesn't work anymore with new Selenium versions.

Thanks ! ;)

PageFactory type missing on netstandard2.0

Hi ,

I've noticed that the PageFactory type is not supported/invisible on netstandard2.0. Are you planning to add the support ?