Reverting setting focusmanager.testmode = true by default in FF.
Refactoring asynchronous execution of JavaScript in IE driver

This introduces a new method for executing JavaScript functions
asynchronously via a new thread. This centralizes the code used to execute
automation atoms that may cause an alert to display (like click or
submit).
Unignoring a test that passes in IE
Fixing -log option for all grid modes. Fixes issue 5498
Modified to throw if an element is not enclosed within a form in IE.

This ensures consistent behavior to other browsers.
Increasing timeout for asynchronous JavaScript execution.

This allows more time for automation atoms to complete their operations
before timing out.
Updating .NET form handling tests
Enable various compiler checks for js_fragment builds.
Use capability names from single location
Implements simple color-based tests for Taking screenshots.

* implements new tests
* add logging/error reporting/tracing to IE screenshot atom

Fixes issue #847.
Helps investigate issue #2440
Modified to check the interactable state of an element before clicking.

The clear Automation Atom normally checks that an element is interactable
before attempting to clear it. Unfortunately, when the atom is run on a
separate thread in legacy IE, the error states do not get propagated back
to the calling thread properly. To avoid this problem, the driver will
check the interactable state before calling the clear atom. To facilitate
this, a new atom has been exposed for checking the interactable state.
Modified to check the editable state of an element before clearing.

The clear Automation Atom normally checks that an element is interactable
and editable before attempting to clear it. A previous change fixed the
case for checking the interactable state, but not the editable state. The
driver will now check the editable state as well. To facilitate this,
a new atom has been exposed for checking the editable state.
Merge remote-tracking branch 'googlecode/master'