Closed
Conversation
….NET The .NET bindings were passing an incorrect command-line switch to IEDriverServer.exe for the location to extract embedded library files. Fixes issue SeleniumHQ#5211.
…ugin for IE. Modal dialogs are now checked for existence of the WS_CAPTION style. Note that if IE ever decides to change how it displays alerts, this may begin to cause failures in alert detection. Fixes issue SeleniumHQ#4839.
…ntOverflow atom. Fixes issue SeleniumHQ#2387.
Most of the server-components (chromedriver.exe, IEDriverServer.exe, WebDriver Firefox extension) do not understand how to handle the FileDetector property. They simply approach all file upload as uploading from the local machine. If you need to upload remotely, use an instance of the RemoteWebDriver class.
for an element that is not within a form (currently the test is based on the documented behaviour, but no one of FF, Chrome IE passes this test)
deleteed. Ignored for now because semantics is not defined.
browser names with the references to the constants. Fixes issue 1630
IOUtils.closeQuitely
…build with crazy-fun before commit
…dexecutor understands
…lower than expected rather stopping where we want to.
…hould not be thrown
LogEntry (and dependency on json lib is back too)
This allows the user to set a capability to control how long the IE driver will attempt to locate an IE browser window belonging to the iexplore.exe process launched by the driver. This is to overcome the bug reported by some users that the IELaunchURL Windows API reports the incorrect process ID for the launched iexplore.exe process. In this case, there is nothing the IE driver can do about the problem as the bug is inside IE itself. However, this will allow a user to exit the offending situation early, and attempt to recover. The capability expects an integer value, representing the number of milliseconds the driver will contininue to look for the newly-launched IE window. Setting the capability to 0 (which is its default value) will cause the IE driver to wait indefinitely. The default, "indefinite wait" behavior aligns with the behavior of the IE driver prior to this commit, and doesn't fix the issue per se by setting an arbitrary timeout, but rather gives the user the ability to set their own timeout if desired. Fixes issue SeleniumHQ#4541.
Contributor
Author
|
This should only have had one commit. Closing and re-creating. |
IlyaNaumovich
added a commit
to IlyaNaumovich/selenium
that referenced
this pull request
Feb 11, 2018
yiming-tang-cs
pushed a commit
to ponder-lab/selenium
that referenced
this pull request
Jan 2, 2020
…_ciphers Fix for bug #1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The test name had a typo. There are no other references to this exception in the code, and the test is being discovered dynamically.