Starting with Chrome 33, certain types of input elements do not
support the selection API (in fact, they throw when you try to
access the property). This prevents us from fully simulating typing
in the atoms.

Try to case these cases and throw a more descriptive error, pointing
the user at https://code.google.com/p/chromium/issues/detail?id=330456
so they have the proper context for why typing no longer works as
expected.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=60184506
Escaping backslashes when writing Firefox preferences to profile in .NET

Fixes issue #3283.
Fixing when cookie expiration date received by .NET exceeds max DateTime

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). Fixes issue #5692.
Adding exception handling in .NET WebDriverBackedSelenium

Against my better judgement making any changes here whatsoever.

Fixes issue #4248.
Don't shadow outer lvar
Set LowResourcesMaxIdleTime in Grid to avoid timeout of 'forever'. Fixes issue 6770.
Revert "Set LowResourcesMaxIdleTime in Grid to avoid timeout of 'forever'. Fixes issue 6770."

This reverts commit bfc09170369199101f7b836b610d7595dbc74ae3.
Adding Firefox profile deletion test to .NET
Starting with Chrome 33, certain types of input elements do not

support the selection API (in fact, they throw when you try to
access the property). This prevents us from fully simulating typing
in the atoms.

Try to case these cases and throw a more descriptive error, pointing
the user at https://code.google.com/p/chromium/issues/detail\?id\=324360
so they have the proper context for why typing no longer works as expected

Signed-off-by: AutomatedTester <dburns@mozilla.com>
Modifying to use bot.dom.getOverflowState atom for element overflow.

This is a more reliable and fully tested method than previously used.
There is still a minor issue when the element point in question is
exactly on the overflow border, but this needs to be addressed in the
atoms code, rather than at the IE driver level. Fixes issue #6898.
When the host is unknown, make the HtmlUnitDriver return an error page.

Fixes issue #6512.
Add Keys.chord(Iterable<CharSequence>) as a utility method.

Fixes issue #3991
Exposing process ID of service executablt in .NET DriverService

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. Fixes issue #6699.
Exposing property on .NET PhantomJSDriverService to specify IP address.

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.

Also exposes the ability to specify a Selenium Grid hub with which this
instance of PhantomJS should register as a node.

Fixes issue #5755.
Oops. Commited compile error by mistake
Reorganizing wait algorithm in HtmlDialog.

Now is more correctly aborting the wait if a new (cascading) dialog is
detected. Fixes issue #6744.
No longer redirecting console output for Firefox in .NET bindings.

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. Hopefully, this will help prevent some of
the problems with issue #3719.
Fixing XML documentation comment warnings
Fixing missed redirection of stdout and stderr for .NET Firefox.
merged selenium origin