- From: wolenetz <web-platform-tests-notifications@w3.org>
- Date: Wed, 07 Sep 2016 04:12:00 GMT
- To: public-web-platform-tests-notifications@w3.org
@tidoust @jyavenard Please take a look ASAP. Note that Chromium will not yet pass some of these since https://crbug.com/639144 is not yet fixed. Specifically, each of the following currently triggers the old async remove behavior in Chrome (and hence, the subtests fail): * Test setting same duration multiple times does not fire duplicate durationchange * Test setting the duration to less than the highest starting presentation timestamp will throw * Truncating the duration throws an InvalidStateError exception when new duration is less than the highest buffered range start time of one of the track buffers * Truncating the duration throws an InvalidStateError exception when new duration is less than a buffered coded frame presentation time View on GitHub: https://github.com/w3c/web-platform-tests/pull/3655#issuecomment-245169892
Received on Wednesday, 7 September 2016 04:12:09 UTC