Reinstating execution of JavaScript on separate thread for IE10 on Windows
7.
In Safari 5.1.7, the browser sometimes fails to resolve CSS selectors built
from the document element. Try to detect this and fallback to generating a
random ID for the element that we can reference. To avoid unnecessarily
modifying the DOM, we only use this random ID if the normal selector fails.

Update issue 4996
The underlying issue with SafariDriver and sendKeys is fixed, but I still
need to publish a new prebuilt.  Expect this fix to be available in the
2.32.0 release.
Push a new prebuilt SafariDriver. Also pre-emptively bumping the version in Info.plist to 2.32.0
Update to the latest version of the Closure compiler. This required a few around changes to account for new checks enforced by the compiler (mostly the syntax of type casts).
Implementing formatters for isAlertPresent and isConfirmationPresent
commands
For Promises/A+ compatibility, allow rejection reasons to be any value.
Rename resolve(d) -> fulfill(ed). Deprecated resolve will be deleted in 2.34.0
The new Closure compiler allows you collapse @type and @private
annotations:

/**
 * @type {string}
 * @private
 */
var foo = '';

/** @private {string} */
var bar = '';

Remove some clutter from our code base by applying this abbreviated syntax
throughout.  There should be no functional changes.
Remove webbit and jee as direct dependencies of server_very_core: it makes no sense to depend on both
The Apache httpclient is not a dependency of anything in the common library
Minimize the number of third party libraries used by the very heart of the remote webdriver server.
Remove the augmenter from the server-side jar
Extract the driver service from the main remote target
We're requiring java6 now, so workarounds that check for methods only present in java6 are worthless
Change a dependency from RemoteWebDriver to the more accurate HasCapabilities
Base the android apk off the newly cleaned up server core.
Clean up a build file.
Modifying .NET Firefox driver to only look to connect to IPv4 addresses.

ConnectToBrowser() always creates IPv4 addresses to initially connect on.
If an IPv6 address was found in discovering potential IP addresses for
connection, this would throw an exception. Fixes issue #4629.
Changing .NET FirefoxBinary timeout property to use TimeSpan.

Using TimeSpan allows more flexibility for the user to set, and does not
hard-code milliseconds as the unit of measure. This commit introduces
overloads of the appropriate exposed properties and methods, marking those
taking a long as obsolete. The obsolete members will be removed in a
future version.
submit should throw NoSuchElementException if the target element is not
within a form. Implemented in atoms, Firefox and HtmlUnit.