Give each segment equal amounts of time fractions
Change path test to use non-equilateral shape to test unpaced path animation
Rebased test-path expectations
Style fixes, clampify things, implement unpaced timing function, update test-path, test-path-checks needs rebasing
Rebased test path checks
Supply the timed item directly to the paced timing function constructor
Bitshift right instead of parseInt
Fix the following usage of the at() function.

at(1.0, function() {});
at(1.0, function() {}); // Conflict

at(1.0, function() {}, "Check my feet");
at(1.0, function() {}, "Check my feet"); // Conflict!
at(1.0, function() {}, "Check my arms"); // Fine

at(2.0, function() {}, "Check my feet"); // Not conflict
Updating the auto-generated test cases to better utilise the at() desc argument.
Merge pull request #318 from mithro/test-desc-another-attempt-fix

Test desc another attempt fix
Style fixes
Use the tests array in the complete message.

postMessage delivery order is not determanistic (IE you can get a result
message *after* the complete message), so building the results array ourselves
is a bad idea. Plus why do that work when testharness already provides the list
for us!?
Merge pull request #308 from mithro/harness-fix

Use the tests array in the complete message.
Fixed bug when a paced animation effect is modified and the timing function is not updated
Updated path animation test to check animation effect modification
Clean up test path code
Merge pull request #320 from alancutter/pacedPathAnimations

Unpace path animations and implement paced timing
Fixing issue #264 by not loading testharness_timing.js in unittests.

It was descided that unittests should not be time dependent and should not use
at/timing_test functionality.
Fixing Issue #313 - at doesn't handle NaN gracefully.

Added more checks to the seconds argument for at(). Now makes sure;
 * the number is positive or zero,
 * the number isn't NaN,
 * the number is finite.
Merge pull request #326 from mithro/handle-bad-arguments

Fixing Issue #313 - at doesn't handle NaN gracefully.