|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
Bug 1293186: Do not assume that currentTime is still at seeking position when seeking event is fired.
58 bytes, text/x-review-board-request
|Details | Review|
Noticed during a compilation (-j14) and running the test: http://www.w3c-test.org/media-source/mediasource-play-then-seek-back.html failure was https://github.com/w3c/web-platform-tests/blob/master/media-source/mediasource-play-then-seek-back.html#L34 assert_equals(mediaElement.currentTime, 0.0, 'Current time is 0.0'); in the 'seeking' event handler. What is the proper behaviour here. Is it correct to assume that currentTime will be the seek time as the seeking event is fired? Reading the spec, I only see requirement for the currentTime to be stable within the same event loop
Comment on attachment 8778786 [details] Bug 1293186: Do not assume that currentTime is still at seeking position when seeking event is fired. https://reviewboard.mozilla.org/r/69956/#review67092
Attachment #8778786 - Flags: review?(jwwang) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/4fa9a49c57aa Do not assume that currentTime is still at seeking position when seeking event is fired. r=jwwang
Conclusion: the test is invalid, fixing the test.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox51: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
You need to log in before you can comment on or make changes to this bug.