Don't fail tests if progress can't be rendered

This allows mocha to be used on Firefox < 3.5
Fix indentation in clean utility

utils.clean extracts a test method content re-indenting the function for whitespaces.
This commit fixes to issues with indentation

* windows line feed `\r\n`
* tab indentation `\t`
Return true from window.onerror handler

Mocha's own error reporter will report the error; it shouldn't
be printed to the console, trigger an error badge on the Firebug
toolbar button, etc.
Expose only the specified UI in the browser

When instantiated in the browser, Mocha registers the "BDD-style"
interface. Since an explicit call to the browser-specific `mocha.ui` is
required, the original registration is invalid. Prevent that UI from
reacting to the `pre-require` event (and exposing its API).
introduced mocha.throwError for better async error handling
Removed duplicate test output for multi-line specs
Fix should to be 2.0.x
Fix test for breaking change in should 2.0.x (fix #1013)
Mocha.ui() now tries to import ui module if name is not found in mocha.interfaces
Update history.md
Release 1.14.0
Add faster Runner.prototype.globals(arr) (close #1024)
Add --no-exit flag to prevent process.exit() call (close #1018)
Wraps long lines in test results. (fix #1030, close #1031)
Fix for NaN coming in time attribute when test fails.
add Runnable.globals(arr) method for per test global whitelist

Instead of suite wide whitelisting of global leaks, this allows for
individual tests to whitelist globals. This allows for keeping global
detection for tests which are not expected to set globals while allowing
for certain globals if the author expects a test to set globals
Fix inline diffs (close #1044)
Update bower and component versions to 1.14.0 (close #1042)
Fix yui compression (fix #1035)
Correct erroneous test

Because the Runnable under test is not part of a Suite, its context is
undefined. Prior to this commit, the error returned was a
runtime-generated `ReferenceError`, not a Mocha-generated `Error`.

Set the timeout via the `Runnable#timeout` method, and update the test
to assert the correct behavior (not implementation details such as the
message body of the generated error).