reverting d67c06d65bd53d62d6c0eeecce74eac65af1caf6. servlets do apply to hub & node
Updating .NET ClickScrollingTest to match Java tests
Attempting to correct IE6 javascript atoms tests
Adding toString to Color
Fixing memory leak on grid node. It is a temporary fix, LoggingManager
needs to be rethinked as the whole. Fixes issue 4969
Adding a guard to a logging test that should fail in chrome with
chromedriver1
Setting requireWindowFocus to true when running tests on Sauce
Upgrade OperaDriver to 1.3, which uses Selenium API 2.32
Removing deprecated code
Adding unhandled alert text to the exception message. Fixes issue 5652
Implementing deserialization for UnhandledAlertException with no enclosed
Alert object
Fix broken build by declaring symbol used in type annotation, but not goog.require'd
Disabling two recently added tests in Opera
Minor code refactoring. Fixes issue 4128
Simplifying top frame search. Fixes issue 5576
Replace distutils.dir_util by shutil

Using distutils in runtime code is not a good idea. distutils.dir_util
writes a verbose log and causes test cases that are being run via
'setup.py test' to create a lot of unneeded log output that can not be
suppressed easily. shutil.copytree and shutil.rmtree do the same as
the functions in distutills.dir_util without producing any log output.
supporting Store command in WebDriver playback. Fixes Issue 5653
Correcting .NET IE-specific test to properly handle alert
Prevent double-clicks when using WebElement.click().

When using the requireWindowFocus capability, it's possible that
multiple calls to WebElement.click() might happen too quickly, and they
might be interpreted as a double-click. This change inspects the last
time an element was clicked on, and if it is within the system double-
click time, it waits until that time passes before performing the second
click.
Making InputManager more robust in the requireWindowFocus case.

Previously, using the Windows SendInput API could cause keystrokes and
mouse events to be added to the system message queue, but would return
back to the caller before those events were processed by Internet
Explorer's message loop. This change adds a Windows mouse hook and
keyboard hook to monitor when the messages are processed by an
applications message loop. There is still a potential race condition, and
users may still need to execute some local synchronization code.