Selenium.Support changelog and release notes, page 3 | NuGet

NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →

3.14.02 Aug 2018Deprecated

Additionally, the DesiredCapabilities class is now marked as deprecated and will generate a compile warning on its use.

Refactored .NET capability handling. This version introduces a large and intrusive refactor of the .NET bindings' capability handling. It introduces a new class, RemoteSessionSettings, for use with creating remote sessions via RemoteWebDriver. Additionally, the DesiredCapabilities class is now marked as deprecated and will generate a compile warning on its use.

Almost without exception, users should not be using DesiredCapabilities in .NET. The browser-specific options classes provide functionality for adding any additional capabilities that would need to be sent to a remote end. One possible exception is when using RemoteWebDriver to connect to a remote server implementation, where the ToCapabilites method has been called, but the user wants to add additional capabilities, even though they could and should have been added before calling the method. In a future release, calling ToCapabilities will result in a read-only capabilities object, but recognizing that many users already have existing code that does this, moving immediately to make the returned object read-only is premature. For the moment, then, the SetCapabilty method is now marked as deprecated on DesiredCapabilities. In the next version of the .NET bindings, the return from ToCapabilities will be changed to return a read-only object.

The RemoteSessionSettings class is designed for use cases where the user wants to create a remote session using RemoteWebDriver where all of the nodes in the session creation support the W3C WebDriver Specification dialect of the wire protocol. This class is designed to be used in conjunction with the browser-specific driver options classes for matching capabilities on the remote end.

For single-browser cases, it is still possible (though unnecessary) to use a browser-specific driver options class (ChromeOptions, FirefoxOptions, etc.) by calling the ToCapabilities() method, but as previously mentioned, in the future, the capabilities returned will be read-only, and will not be able to be added to. Users who feel the need to modify the options class after converting to capabilities are encouraged to add the additional capabilities to the options class before the conversion by appropriate use of the AddAdditionalCapability method.
Exposed additional extension points to better control HTTP communications between the language bindings and the remote end implementation. For the .NET implementation of HttpCommandExecutor, we now expose a Proxy property for proxying requests between the .NET code and the remote end WebDriver implementation. Note carefully that this is entirely separate from the proxy used by the browser for monitoring communications between the browser and the server hosting the page being automated.

Additionally, this change exposes the IsKeepAliveEnabled property to make it easier to set whether or not the "keep alive" header is sent when communicating between the language bindings and the remote end WebDriver implementation.

Finally, for local use, the DriverServiceCommandExecutor now exposes a property to allow the user to set tho newly-exposed properties by allowing access to the internal HttpCommandExecutor of the driver service.
Added a workaround for Safari Tech Preview to send the proper browser name to the driver.
Added type-safe properties for Safari capabilities in .NET SafariOptions.
Marked .NET hardware manipulation interfaces deprecated. The Mouse Keyboard, and TouchScreen properties were never intended for direct use in users' code. These interfaces, and the properties that reference them, are now being marked as deprecated. The correct way to simulate advanced user input is to use the Actions or ActionBuilder classes.
Removed long-deprecated local PhantomJS support from .NET, as well as other deprecated code.

Open source →

3.13.025 Jun 2018

(on behalf of Jake Durand) Replaced Chrome with Firefox in .NET documentation comments.

(on behalf of Jake Durand) Replaced Chrome with Firefox in .NET documentation comments.
(on behalf of Michael Keeley) Modified to allow extension of RemoteWebElement for caching properties. This approach is not one with which the Selenium development team is entirely comfortable, and downstream projects are strongly encouraged to prefer composition over inheritance.
Reinstated ICommandExecutor descending from IDisposable. Now that the Appium project has implemented the methods required by an implementation of IDisposable, this change can be made upstream in the Selenium project. As this change has been rolled back once before to accommodate downstream projects, it will be incumbent upon them to update their libraries now, as it will not be rolled back again. In the case of Appium, this is merely awaiting a binary release; other downstream projects will be responsible for managing their own code changes and release schedule.
Removed legacy WebDriver extension when using Geckodriver. When a FirefoxProfile object is created in the .NET bindings, the legacy WebDriver extension is included in that profile by default. This includes the case where the user is using Geckodriver. When using Geckodriver, the legacy extension is doing nothing more than taking up space. This commit adds an internal method to detect when a FirefoxProfile object is being used with geckodriver, and removes the extension from the list of extensions in the profile before the profile is serialized to disk, and subsequently to a base64-encoded string for transmission over the wire to geckodriver. Fixes issue #6043.
Updated EdgeOptions to include type-safe properties for Edge-specific capabilities.
Added property to force use of legacy protocol for Safari. Starting with Safari Technology Preview 58, and continuing with the driver released with Safari 12, the driver executable uses the W3C Specification dialect of the prototcol by default. It includes a command-line switch, however, to force the use of the legacy open-source project dialect of the protocol. This commit adds a property to the SafariDriverService object allowing users to set that command-line switch. Note that if this property (false by default) is set to true for a version of the driver that does not support the switch, it will cause errors. If set to false, the .NET bindings do not modify the safaridriver command line at all.
Fixed mouse movement in .NET. The previous commit to the mouse movement for .NET changed the optional element ID from null to the empty string. This is incorrect. If no element is specified in the move (for non-spec-compliant driver), omit the ID altogether.
Fixed null pointer exception for .NET on Safari with mouse movements.
(on behalf of Clay Martin) Fixed quit command for default state of Edge driver.

Open source →

3.12.08 May 2018Deprecated

The previous event and event args are marked as deprecated for removal in a future release, and the previously named event is now a no-op, and will ne…

Updated unhandled JavaScript errors to throw WebDriverException in .NET.
Added option for .NET EdgeDriverService to use W3C protocol dialect. The Microsoft Edge driver specifies the use of the W3C WebDriver Specification dialect of the JSON wire protocol via a command-line switch. This commit exposes that behavior in the form of a property on the EdgeDriverService object. Note that this command-line switch is only valid for versions of the driver executable for Windows 10 versions later than the 2018 Fall Creators' Update version (this is the code-named "Redstone 4", or "RS4" builds). Attempting to use this property with versions of MicrosoftWebDriver.exe before RS4 will result in errors, as the driver executable will not start properly with an unknown command-line switch. This commit also makes use of the fact that in RS4 and beyond, the driver executable is a feature that is installed in the OS, not a separate download, so the test projects have been updated to reflect this.
Added default value to .NET IE element scroll behavior option.
Changed 'unhandled error' status code to throw WebDriverException in .NET. Previously, this error code would throw an InvalidOperationException.
(on behalf of Christopher Wood) Fixed ExecuteScript and Actions to handle IWrapsElement appropriately. Using EventFiringWebDriver, element targets and args throw exceptions when calling ExecuteScript or Actions methods. This is fixed by casting as IWrapsElement and checking for wrapped elements first. Fixes issue #5810.
Refactored creation of RemoteWebElement to use a factory. Previously, the RemoteWebDriver class had a protected method called CreateElement that took the element ID as a parameter and returned a RemoteWebElement object. That approach is not flexible enough for some downstream projects that implement their own subclasses of RemoteWebDriver and RemoteWebElement. To rectify that, this commit replaces the calling of CreateElement with the use of a RemoteWebElementFactory class that handles the creation of RemoteWebElements. Note carefully that the CreateElement method still exists, so as to prevent compile-time errors for downstream consumers, that method is no longer called. If you are a user who has overridden that method as part of your project, you'll need to create an implementation of RemoteWebElementFactory that creates your custom subclass of RemoteWebElement.
(on behalf of Jacob Kiesel) Fixed obscure window switching bug. This change fixes searching by window name if the current window handle becomes invalid and the name being switched to does not exist.
Fixed .NET HttpCommandExecutor event for RemoteWebDriver. This change moves the firing of the event raised before sending a remote HTTP request to before the setting of the request body. This allows the request settings to be properly set without throwing an exception. This commit also renames the event and event args object to SendingReomteHttpRequest and SendingRemoteHttpRequestEventArgs, respectively. The previous event and event args are marked as deprecated for removal in a future release, and the previously named event is now a no-op, and will never be fired, even if a handler is attached.

Open source →

3.11.16 Apr 2018

Added option to tell ChromeDriver to use the W3C WebDriver protocol dialect instead of the legacy open-source dialect.

Added option to tell ChromeDriver to use the W3C WebDriver protocol dialect instead of the legacy open-source dialect.
(on behalf of Phillip Haydon) Updated doc strings for FirefoxDriver to no longer refer to ChromeDriver
Corrected remote URL for IWebElement.GetScreenshot() method.
Made ICommandExecutor interface extend IDisposable.
Fixed serialization of proxy autoconfig URLs. Fixes issue #5050.
Reverted .NET bindings to send spec-compliant new session for all browsers. Now that the Java remote server will correctly handle spec-compliant new session payload, even for browsers that are not yet spec-compliant, we can revert to the original behavior of sending both "capabilities" and "desiredCapabilities" properties with new session requests. Reverts commit 4ce57f6.
Modified to guard against assembly location being empty. When looking for supporting files on disk, the bindings look in the "current working directory" where the assembly is written. However, if the assembly has been embedded in an executable as a resource, and extracted into memory at runtime, the location will be blank. This commit prevents the exception being thrown, at the expense of possibly looking in the wrong directory.
Added locking for lazy-load of static dictionary. When running in parallel, there is a chance that multiple threads could attempt to populate a static dictionary used for translating error codes. This commit adds locking around the initialization of the static dictionary. Note that we are not using "double-check" locking, but the locking we use should be good enough. Fixes issue #3166.
(On behalf of John Chen) Fixed ChromeDriver NetworkConditions setter. The JSON object generated by the .NET version of ChromeDriver NetworkConditions setter had incorrect format, and was rejected by ChromeDriver.
Added sending a user-agent string for .NET remote HTTP requests to a remote end (Java standalone server, IEDriverServer.exe, chromedriver.exe, geckodriver.exe, etc.). Addresses #5657 for .NET.
Fixed .NET ChromeDriver network conditions commands URLs. Fixes issue #5693.
Added BeforeRemoteHttpRequest event to .NET RemoteWebDriver. This commit adds the ability for advanced users of the .NET bindings RemoteWebDriver class to modify the HTTP command sent from the .NET WebDriver code to the remote WebDriver server. Note carefully that this DOES NOT modify the HTTP request between the browser and the web server, and is not a mechanism for getting access to that HTTP request. Usage of this new event would look something like this:

public void StartDriver() { HttpCommandExecutor executor = new HttpCommandExecutor( new Url("http://localhost:4444/wd/hub"), TimeSpan.FromSeconds(60)); executor.BeforeRemoteHttpRequest += BeforeRemoteHttpRequestHandler; ICapabilities capabilities = new ChromeOptions().ToCapabilities(); IWebDriver driver = new RemoteWebDriver(executor, capabilities); }

public void BeforeRemoteHttpRequestHandler( object sender, BeforeRemoteHttpRequestEventArgs e) { // Note: WebRequest.DefaultWebProxy is an IWebProxy implementation. // This could be anything, from adding additional headers, to modifying // the content of the request. Use with extreme caution. e.Request.Proxy = WebRequest.DefaultWebProxy; e.Request.AutomaticDecompression = DecompressionMethods.GZip }
(On behalf of Samuel Bétrisey) Add support for Basic Access Authentication in .NET RemoteWebDriver. The username and password of the Uri wasn't used by the HttpWebRequest. Usage example:

new RemoteWebDriver(new Uri("http://user:pass@example.com/wd/hub"), DesiredCapabilities.Chrome());
(On behalf of "granak") Null cookie value fix. Cookies with empty string values would throw exceptions.
Enabled reconstitution of .NET FirefoxOptions from raw capabilities. This is a temporary measure until DesiredCapabilities is done away with for good. Fixes issue #4855.
Modified to write screenshots using the Save overload that takes a System.IO.FileStream object. Rather than using the Image.Save overload that takes a string containing the file name, we should use a FileStream. The FileStream object handles validating the existence of the path to which one is attempting to write, so this will avoid the cryptic GDI+ error that occurs if the file already exists. Additionally, the SaveAsFile method now does what it says on the tin, that the file will be overwritten if it already exists. Fixes issue #4645.
(On behalf of Sean Rand) Added overload argument to the SelectElement.SelectByText method. The XML summary informs that the method provides partial match ability on the options by Text. However this wasn't fully implemented so pushed the ability via a boolean to perform such a partial match on an options list. Fixes issue #3575.
(On behalf of Sean Rand) Added test playlists for each .NET test project in the repo. This is to help aid running of all tests in a specific project. Originally, this was intended to simply add a playlist for the support tests but adding playlists for all of the test projects is a better approach. Fixes issue #3805.
(On behalf of Arnon Axelrod) Added the new value of the element to the ElementValueChanged and ElementValueChanging event args. This commit also creates a new overload of OnElementChanging and OnElementChanged but also keeps the original overloads to preserve backward compatibility. Additionally, the original overloads are marked with the [Obsolete] attribute to let users know they should migrate to the new overloads.
Fixed proxy bypass address serialization for legacy .NET drivers. The W3C WebDriver Specification states that the list of addresses to bypass in a proxy configuration should be an array. The legacy OSS dialect of the protocol specifies it must be a string. This commit fixes the serialization for the non-spec-compliant case, serializing it as a semicolon-separated list. Fixes issue #5645.
Updating .NET to not propagate non-W3C compliant capability names. Fixes issue #5646.
Added new property for geckodriver --jsdebugger command line switch to FirefoxDriverService object.
(On behalf of Christopher Buttkus) Added LeftShift, LeftAlt, LeftControl, Command, and Meta as KeyDown/Up events for .NET
(On behalf of "vflame") Added ability to install Firefox addon using manifest.json. Firefox addons/extensions built with WebExtensions API have a manifest.json instead of install.rdf. When Selenium extract the addon/ extension id, it only looked for install.rdf. This fix adds extracting the addon/extension id from the manifest.json in addition to install.rdf. Fixes issue #4093.
(On behalf of Yevgeniy Shunevych) Fixed AddEncodedExtension methods of ChromeOptions and OperaOptions
Updated .NET strong-named assembly build to correct package references. Fixes issue #5511.
Updated WebDriverBackedSelenium .csproj file to embed resources. This step was omitted when the build process for the .NET bindings was migrated from crazy-fun to Buck. Fixes issue #5528.
Streamlined Actions class. The Actions class will now throw an exception on instantiation if the IWebDriver instance passed into the constructor does not also implement IActionExecutor. This will help folks who wrap the standard WebDriver driver classes to be able to continue to work with the Actions class.

Open source →

3.11.011 Mar 2018

Added support for intercepted element clicks. This adds a new exception, ElementClickInterceptedException to indicate when an element is obscured by a

Added support for intercepted element clicks. This adds a new exception, ElementClickInterceptedException to indicate when an element is obscured by another element. This allows users to distinguish between different causes of elements not being clickable.
Marked .NET ExpectedConditions obsolete. Using the ExpectedConditions class provides no benefit over directly using lambda functions (anonymous methods) directly in one's code. Since the community appears to believe that an "official" repository of wait conditions is desirable, the existing code has been migrated to a new repository under a new organization on GitHub (https://github.com/DotNetSeleniumTools/DotNetSeleniumExtras). It is hoped that this will encourage a volunteer from the community to take ownership of this code. Users should update their references and migrate their code to use SeleniumExtras.ExpectedConditions. This implementation will be removed from the .NET language bindings in a future release
Marked .NET PageFactory obsolete. The .NET implementation of PageFactory is deeply flawed. Additionally, using the PageFactory provides no benefit over other methods of Page Object creation in .NET. This is true for code verbosity as well, which is often the reason cited for wanting to use the PageFactory in .NET. The existing code has been migrated to a new repository under a new organization on GitHub (https://github.com/DotNetSeleniumTools/DotNetSeleniumExtras). It is hoped that this will encourage a volunteer from the community to take ownership of this code. Users should update their references and migrate their code to use SeleniumExtras.PageFactory. The implementation will be removed
Updated .NET Actions class to change element offsets for W3C mouse move. When the Actions class performs a mouse move that includes a reference to an element and an x-y offset, the offsets are calculated differently depending on whether the remote end adheres to the W3C WebDriver Specification. In the W3C case, the offsets are calculated from the center of the element. This differs from the legacy behavior, which calculates offsets from the top-left corner of the element. This change uses the language bindings to allow the user to optionally choose which origin to use, and by default calculates all offsets from the upper-left, if not specified. This normalizes the mouse move behavior across all types of remote ends.

Open source →

3.9.05 Feb 2018

Added commands to get and set network conditions for Chrome in .NET. To get or set the network conditions, use the NetworkConditions property of the C

Added commands to get and set network conditions for Chrome in .NET. To get or set the network conditions, use the NetworkConditions property of the ChromeDriver object. This property gets or sets a ChromeNetworkConditions object which contains the proper values. Fixes issue #5338.
Re-added CLSCompliant attribute to .NET assemblies. When converting from the prior build system to using Buck and the dotnet build tools, the assembly-level CLSCompliant attribute was removed. This commit restores the CLSCompliant attribute to the assembly manifests. Fixes issue #5324.
Removed check for leading hyphens in .NET FirefoxOptions AddArgument. In prior releases of geckodriver, it was a requirement that all arguments be preceded by double hyphens ("--"). Geckodriver has now relaxed that restriction, and the .NET bindings need to keep up with that change. This commit removes the check for leading hyphens when calling AddArgument.
Fixed strong-named assembly references. In the move to using the dotnet build tools instead of calling the C# compiler directly, the creation of strong-named assemblies was broken with incorrect references being created. This commit fixes that problem. Fixes issue #5254.
Exposed HostName property for .NET DriverService class. Previously, the host name for a DriverService was hard-coded to be "localhost." This is normally acceptable, as a DriverService is only intended to be used locally, and most executables that are represented by a DriverService (chromedriver, geckodriver, IEDriverServer.exe, etc.) do not even allow connections from external machines for security reasons. However, there is a legitimate use case (.NET Standard 2.0) where a local IP address ("127.0.0.1" or "::1") is preferable to using the "localhost" moniker. This HostName property allows the user to specify that IP address. Note that the property defaults to "localhost," preserving previous behavior.

Open source →

3.6.025 Sept 2017Deprecated

Removed internal use of deprecated construct in .NET bindings.

Removed internal use of deprecated construct in .NET bindings.
Added no-format override to .NET Screenshot class for saving file, which will save the image in a Portable Network Graphics (PNG) format.
Updating .NET bindings to not send incorrect W3C Firefox capabilities Previously, RemoteWebDriver would send the same capabilities dictionary using both the "desiredCapabilities" and "capabilities" properties when requesting a new remote session. In the case of the language bindings expressly requesting to use the legacy Firefox driver, the capabilities dictionary will include properties that are invalid for the W3C-compliant remote server. To resolve that issue, we will mask the explicit attempt by setting a property that causes the .NET RemoteWebDriver to send a legacy-only compatible new session request when explicitly requesting the legacy driver. Fixes issue #4637.
Added the output of .NET Standard 2.0 class libraries to the release artifacts, which will allow the bindings to be used against .NET Core 2.0. This addition marks the initial support of .NET Core in the Selenium .NET language bindings. Use of the .NET bindings against .NET Core should be considered experimental at this stage. The following issues are already known, and should not be reported:
- Calls to localhost in .NET Core are slower than those in the full .NET Framework. This is due to internal differences in the .NET libraries themselves, and are not the fault of the bindings directly. See https://github.com/dotnet/corefx/issues/24104 for more details.
- Attempting to save a screenshot to any graphics file format other than Portable Network Graphics (PNG) will throw an exception. .NET Core does not provide the image manipulation classes that the full .NET Framework does, and there are no production-ready third-party libraries that provide that functionality yet and also only rely on managed code. This concern is over and above the difficulties with adding dependencies to the language bindings.
- When using the bindings against .NET Core, there is no PageFactory class available. This is not an oversight, nor is it a bug. The .NET PageFactory implementation requires use of classes that are not available in .NET Core. It is a non-trivial matter to add additional dependencies to the .NET bindings, so simply replacing those classes with a third-party library that is compatible with .NET Core is not a perfectly obvious option.
- References to the .NET Standard 2.0 library versions provided in this and future releases are only valid when using NuGet package references. Simply copying the assembly and adding an assembly reference to the .NET Core 2.0 project will not work. This is by design of the .NET Core ecosystem, which is now entirely dependent on NuGet to properly resolve dependencies.

Open source →

3.4.021 Apr 2017

Exposed new Interactions framework. This release introduces a new Interactions framework using the ActionBuilder class for creating advanced user inte

Exposed new Interactions framework. This release introduces a new Interactions framework using the ActionBuilder class for creating advanced user interaction sequences in the .NET bindings. This framework is only designed to be used with remote ends that understand the W3C WebDriver Specification actions end point, and as such, there is no documentation or guidance for its use at present. Most users will continue to use the Actions class for now,bwhich works with both protocol dialects. Once most remote ends use the W3C dialect of the wire protocol, these classes will become more useful.
Fixed IAlert.SendKeys to send a string instead of a character array when communicating with remote ends that use the in the W3C Specification dialect of the wire protocol.
Now the "marionette" capability is only set for the case where the user wants to use the legacy Firefox driver. Starting with Geckodriver 0.16, this capability is not recognized as valid, since it violates the spec, and will not create a session if it's specified.
Updated InternetExplorerOptions to send IE-specific capabilities in a property named "se:ieOptions". This is the correct method for passing browser-specific capabilities according to the W3C WebDriver spec. This should be transparent for most users, but beginning with 3.4.0.0 of the IE driver, this is the preferred mechanism for passing IE-specific capabilities.
Added "acceptInsecureCerts" capability for use with remote ends that adhere to the W3C WebDriver Specification. The default for the capability is true.
Updated FirefoxDriver(FirefoxOptions) constructor to allow the user to specify UseLegacyImplementation = true in the FirefoxOptions passed to the constructor and not be forced to have a copy of geckodriver available. Fixes issue #3597.
Updated bindings to properly use the W3C WebDriver Specification.

Open source →

2.46.04 Jun 2015Breaking

Finally, this commit also introduces a breaking change in IElementLocatorFactory. Developers of classes that implement this interface will now be requ…

Supports native events for Firefox version 31 (immediately previous ESR). Native event support has been discontinued for versions of Firefox later than 33. Synthetic events tested on Firefox versions 31 (immediately previous ESR), 37 (immediately previous release), and 38 (current release, and current ESR).
(on behalf of Darrin Cherry) Modified ExpectedConditions class to more closely mimic the one provided by Java.
Added ToString override to Platform class. Fixes issue #580.
Removed Firefox profile cleaning step when launching Firefox. Firefox used to require launching to clean up potential issues with the anonymous temporary profile that we use with the driver. This is no longer the case.
Added type safe support to InternetExplorerOptions for page load strategy.
Added ability to get wrapped IWebElement from SelectElement. When using a SelectElement wrapper class to manipulate <select> elements, the user previously had to keep a separate reference to the IWebElement representing the actual element. The SelectElement class now implements IWrapsElement, exposing the WrappedElement property, which gives the user the ability to access the underlying IWebElement. Fixes issue #350.
(on behalf of clz.livio) Added additional PhantomJS command-line options. Added the ProxyAuthorization property and SslCertificatesPath property to the PhantomJSDriverSerivce class. These translate to the --proxy-auth and --ssl-certificates-path command line options on PhantomJS respectively.
(on behalf of clz.livio) Improved DriverService to check response on startup. A driver using a driver service will now throw a WebDriverException if it cannot start the driver service, or if the service executable returns an invalid response. Note that the checks for the validation of the responses is minimal, checking for the Content-Type header and that the response code is a 200.
(on behalf of Sergey Tikhomirov) Refactored PageFactory implementation, including a number of changes to make it more extensible and more robust.

First, instead of the hand-rolled proxy classes that had been used previously, this refactor introduces proxy objects based on System.Runtime.Remoting.Proxies.RealProxy, which allows for more flexibility in the types of objects proxied.

Second, this refactor now allows users to provide their own implementation engines for examining attributes of Page Object classes and determining what course to take. To create a new implementation the user must provide an implementation of the IPageObjectMemberDecorator interface, which determines which attributes to examine fields and properties for, and how to create the proxy objects assigned to the members.

Third, this refactor introduces a new IElementLocator interface to Page Object implementations, and deprecates the IElementLocatorFactory interface. The IElementLocator interface is substantially similar to the now-deprecated IElementLocatorFactory, but requires implementations to provide a property to retrieve the ISearchContext implementation used to actually find elements. The implications of this change are that IElementLocator implementations will need to keep a reference to the IWebDriver or IWebElement they are using. Recommended practice is for this context to be passed in via a the IElementLocator implementation's constructor, and this technique is demonstrated in the source code to the two implementations provided in the regular .NET language bindings releases.

Finally, this commit also introduces a breaking change in IElementLocatorFactory. Developers of classes that implement this interface will now be required to implement the CreateLocator method, which will return a valid IElementLocator implementation. This is to prepare for the removal of the IElementLocatorFactory interface and its implementations in a future release.
Added FindsByAllAttribute to .NET PageFactory implementation. This allows the user to specify that an element must match the criteria of all of the FindsBy attributes a property or field is marked with in order to be found by the PageFactory. Previously, a class member marked with multiple FindsBy attributes would find an element matching any of the attributes' criteria. Because of the nature of this change, you cannot use FindsBySequence and FindsByAll on the same class member. Attempting to do so will result in an exception when InitElements is called.
(on behalf of Immanuel Hayden) Added support for ByAll, finding elements matching all locators.
(on behalf of Chris Block) Changed ExecuteJavaScript extension method for converting result, so that it now validates that the ExecuteJavaScript extension method will correctly detect if the script result is convertible to the generic type.
(on behalf of Yi Zeng) Added constructor overload which takes in single DriverService parameter. This pattern was already implemented in PhantomJSDriver, but not yet in ChromeDriver and InternetExplorerDriver.
Added ability to add custom wire protocol commands in .NET bindings. This allows projects that use a WebDriver-like JSON-over-HTTP wire protocol to add additional end points for their use. It does this by exposing (and renaming) a formerly internal method on the singleton CommandInfoRepository class. To add additional commands, one would call the TryAddCommand method, which is now public. Fixes Google Code issue #8594.
Added ability to handle W3C spec compliant element serialization.
(on behalf of Eberhard Beilharz) Made PhantomJS driver more cross-platform aware. On Linux the filesystem is case-sensitive and executables don't end with ".exe". This change modifies the PhantomJSDriver to search for "phantomjs" on Unix systems while keeping the filename "PhantomJS.exe" on Windows. This allows to use the default constructor of the PhantomJSDriver class on Linux. Previously using the default c'tor resulted in an error that "PhantomJS.exe" can't be found.

Open source →

2.45.027 Feb 2015

Supports native events for Firefox versions 31 (current ESR), and 24 (immediately previous ESR). Native event support has been discontinued for versio

Supports native events for Firefox versions 31 (current ESR), and 24 (immediately previous ESR). Native event support has been discontinued for versions of Firefox later than 33.
Removed automatic installation of SafariDriver extension for .NET. From this point forward, users are expected to manually install the SafariDriver extension into their Safari installation in order to drive the browser. This is due to Apple's changes in architecture for Safari extensions.
Added initial implementation of .NET bindings OperaDriver. The .NET bindings will now support the Chromium-based Opera driver without requiring the use of the Java remote WebDriver server. This driver will work with Opera 26 and above, and requires the download of the Opera driver executable. Code cleanup and refactoring will take place under a separate commit. Note that there is still no support in the .NET bindings for the Presto-based Opera without using the remote server, nor is there likely to be.
Added option to not delete anonymous Firefox profile in .NET. This change adds an option to the .NET FirefoxProfile class so that the driver will not delete the anonymous profile created by the driver. Since the driver cannot and should not use an existing profile in situ because of the multiple instance automation case, this change means that modifications applied to the anonymous profile can be retained and used in future anonymous profiles. The implication is that the user can now make modifications to a profile, and retain those profile modifications (e.g., cookies) into other future profiles, simulating persistent changes over multiple browser launches. Fixes issue #7374.
Introduced type safe option in InternetExplorerOptions to set the capability to disable check of mime type of the document when setting cookies. When setting cookies, there is a check in the IE driver to validate that the page in the browser is, in fact, an HTML page. Despite the fact that omitting this check can cause unrecoverable crashes in the driver, there is demand for a mechanism to disable this check for older, legacy versions of Internet Explorer. Fixes issue #1227.

Open source →

2.40.019 Feb 2014

Supports native events for Firefox versions 27 (current), 26 (immediately previous), 24 (current ESR), and 17 (immediately previous ESR)

Supports native events for Firefox versions 27 (current), 26 (immediately previous), 24 (current ESR), and 17 (immediately previous ESR)
Issue #1175: Implemented ByIdOrName in .NET support package.
Issue #3283: Escaping backslashes when writing Firefox preferences to profile in .NET
Issue #3719: No longer redirecting console output for Firefox. This information was largely unused by anyone, and the implementation had a chance to produce deadlocks when reading from the console output stream for stdout and stderr.
Issue #4248: Added exception handling in .NET WebDriverBackedSelenium.
Issue #5692: Fixed when cookie expiration date received by .NET exceeds maximum DateTime value. When receiving a cookie via the JSON wire protocol, the expiration date is represented as the number of seconds after 12:00:00 AM January 1, 1970 GMT. When a number greater than or equal 253402300800, this is larger than the maximum value of .NET's DateTime value. This change catches the ArgumentOutOfRangeException and forcibly sets the expiration to DateTime.MaxValue (12:59:59 PM December 31, 9999 GMT).
Issue #5755: Exposing property on .NET PhantomJSDriverService to specify IP address on which to listen for connections. When specifying a port on which PhantomJS should listen for WebDriver commands, the user has the option to also specify an IP address to which to bind to listen. This commit exposes that ability. It also exposes the ability to specify a Selenium Grid hub with which this instance of PhantomJS should register as a node.
Issue #6343: (on behalf of Ulrich Buchgraber) Make .NET DefaultWait stop swallowing original exception stack trace.
Issue #6699: Exposing process ID of service executable in .NET DriverService class. This allows the user to attempt to add the process to a Windows job object if they so desire, which will automatically kill child processes when the parent process is exited. Note that job objects are subject to security restrictions when used on Windows Vista or later.
Issue #6860: Updating .NET SafariDriver browser launch code. The initial start page from the temp directory that launches the WebSocket is loaded in Safari via a command line parameter. If the path contains a space, the load will fail. This is fixed by surrounding the temp file name with quotes.
Issue #6870: Updated FirefoxDriver constructor for ICapabilities. This allows the user to pass an ICapabilities object to the Firefox driver constructor and have specific capabilities used in driver instantiation.
Issue #6935: Changing .NET random temp file generation to be truly random. The .NET bindings now use GUIDs as part of the file names for files and directories created in the temp directory. This is to work around potential collisions in random number generation encountered when using the .NET Random class, particularly in different processes. GUIDs are used as their generation in the .NET Framework is optimized for performance.
Issue #6966: Changed .NET WebDriverBackedSelenium OpenWindow to mimic Java. The JavaScript evaluated by the .NET WebDriverBackedSelenium OpenWindow command handler should return a null value from the eval() of the JavaScript to open the window. This is what the Java implementation does, and this commit brings the .NET implementation into line with that.
Updated .NET PhantomJS driver to be able to execute code in the PhantomJS context. This allows the user to execute PhantomJS-specific commands using the PhantomJS JavaScript API.
Updated .NET bindings to use webdriver.json for default Firefox profile. Other language bindings have been using a common JSON file containing the default profile setting for the anonymous Firefox profile used by the Firefox driver. The .NET bindings now do the same.
Now provide an option to hide command prompt window for driver service executables (IEDriverServer.exe, chromedriver.exe, etc.) in .NET bindings.
Modified to allow user to specify name of driver service executable in .NET. We now give an overload to CreateDefaultService for ChromeDriverService, PhantomJSDriverService, and InternetExplorerDriverService to allow the user to specify the name of the service executable. This is particularly useful for non-Windows platforms where the executable does not end with '.exe'. It also allows the user to rename the executable to a name of their choosing and still be able to use it from the .NET bindings.
Added a type safe option for IE to use ForceUseShellWindowsApi.
Updated .NET ChromeOptions to include latest options for Chrome. Also fixed the AddAdditionalCapability method to correctly add additional options to the chromeOptions object passed to chromedriver.exe, instead of to the top- level of the capabilities object. Adding new top-level capabilities is handled by a new overload of AddAdditionalCapability that contains a boolean argument to indicate that the capability should be added to the root of the capabilities object. This handles the 80% case where new "experimental" options are added by the chromedriver team.
Implemented FindsBySequence attribute for .NET PageFactory. This new attribute allows the user to mark a field or property in a page object such that any FindsBy attributes set on the member are used in sequence, as specified by the Priority property. Note that when not specifying a Priority value, or specifying multiple FindsBy attributes with the same Priority value, the behavior is undefined.
Fixed cleaning up leftover temp directory when using SafariDriver.

Open source →