Remove assertion for HTMLMediaElement.seeking in the seeking event
Added idlharness tests for the MSE spec.
Remove pass conditions from currentTime test names

This made it clear that the negative test was already covered.
Merge pull request #716 from foolip/currentTime-test-names

Remove pass conditions from currentTime test names
Update to latest upstream testharness.js.
Simplify and tighten the test for seeking to a negative time
Updated to latest upstream wptserve.
Updated to latest-latest upstream wptserve.
Test seeking to Number.MAX_VALUE
Use movie_5.* instead of movie_300.* wherever possible

movie_5.* is faster to load, so is preferable where possible. All of the
tests already also use audio_5.*, which are even smaller, so this ought
not to expose any new problems. None of the test descriptions seem to
indicate that a big or slow-loading resource is required.
Remove common/domtestcase.js (unused)
Remove pass condition from some media test names
Merge pull request #723 from foolip/rm-media-pass-conditions

Remove pass condition from some media test names
Merge pull request #721 from foolip/movie_300

Use movie_5.* instead of movie_300.* wherever possible
Merge pull request #722 from foolip/rm-domtestcase

Remove common/domtestcase.js (unused)
Merge pull request #719 from foolip/seek-to-max-value

Test seeking to Number.MAX_VALUE
Merge pull request #717 from foolip/seek-to-negative-time

Simplify and tighten the test for seeking to a negative time
Add descriptions for asserts in the seek-to-currentTime test
Merge pull request #709 from foolip/seeking-in-seeking

Remove assertion for HTMLMediaElement.seeking in the seeking event
cc Made a couple of test cases valid.