0567aa4d8716426764a4b9e1f479c5d983444b3d: mybase draft
Xidorn Quan <quanxunzhen@gmail.com> - Wed, 04 Feb 2015 08:24:16 +1100 - rev 398994
Push 25698 by xquan@mozilla.com at Wed, 10 Aug 2016 06:37:20 +0000
mybase MozReview-Commit-ID: AIse40brXhE
a9aff4beaed913f516641f7003e3dc2ca31d15bc: Bug 1277788 - Part 2. Correct mochitest. draft
cku <cku@mozilla.com> - Wed, 10 Aug 2016 13:12:27 +0800 - rev 398993
Push 25697 by bmo:cku@mozilla.com at Wed, 10 Aug 2016 06:33:32 +0000
Bug 1277788 - Part 2. Correct mochitest. MozReview-Commit-ID: CI7W7rPwirf
a8ca7f128bb67778738cbb673148d04274faac96: Bug 1277788 - Part 1. Set initial value of mask-position as center. draft
cku <cku@mozilla.com> - Tue, 19 Jul 2016 15:09:47 +0800 - rev 398992
Push 25697 by bmo:cku@mozilla.com at Wed, 10 Aug 2016 06:33:32 +0000
Bug 1277788 - Part 1. Set initial value of mask-position as center. MozReview-Commit-ID: BflQ6tz8ZjM
50e696408c8f289bb13b2e667d359dde6d9e144c: Bug 1293613: amend expected MSE web-platform-tests expected results. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 15:20:25 +1000 - rev 398991
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: amend expected MSE web-platform-tests expected results. r?gerald They should all run properly now. MozReview-Commit-ID: YLjQ8jkNcf
faebbe1f91970aba07ca9ac4278d9be43c441f63: Bug 1293613: Don't assume that once playing event has fired, the earlier appendBuffer has completed. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 15:10:47 +1000 - rev 398990
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Don't assume that once playing event has fired, the earlier appendBuffer has completed. r?gerald The two operations are asynchronous and independent. MozReview-Commit-ID: D2woSoIzE6p
b2e1a4e04d0063a5261378c6763e4ea82e2b5a46: Bug 1293613: Update test using new manifest details. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 14:43:24 +1000 - rev 398989
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Update test using new manifest details. r?gerald Do not assume that the element is still seeking when the seeking event is actually fired (the seeking operation is asynchronous) MozReview-Commit-ID: Ap24kUQK8R2
0d2539620b9e6b581827eb9bf6f086c43a3afa0f: Bug 1293613: Make liveseekable test run. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 14:22:11 +1000 - rev 398988
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Make liveseekable test run. r?gerald - No html document existed, preventing the test to run. - Remove test related to the updating attribute being cleared: see https://github.com/w3c/media-source/issues/118 MozReview-Commit-ID: GxOBnr5mqyh
bae92d4ea0375d84c5cc5accbc977b76ea0637b1: Bug 1293613: Don't assume that all videos start at 0. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 13:22:35 +1000 - rev 398987
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Don't assume that all videos start at 0. r?gerald See issue https://github.com/w3c/web-platform-tests/issues/1939 MozReview-Commit-ID: LgDQRS8Xz3L
24795ce0dc1ee98ed090fdb0a7efda0d8e692e4d: Bug 1293613: Don't assume all segments audio and video track start at the same time point. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 12:12:08 +1000 - rev 398986
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Don't assume all segments audio and video track start at the same time point. r?gerald Audio track and video tracks have under most cases a different start and end time. Additionally, the mp4 file is poorly muxed and contains out of order frames. As such we keep a table of time and duration for each media segments. The test itself was right, however it had an invalid time table to start with as it incorrectly used the dts (decode timestamp) instead of the pts (presentation timestamp). MozReview-Commit-ID: G2uwK3rroj3
ff0d774a6fda98257d6a177187d8ac53a9609202: Bug 1293613: An invalid or revoked MediaSource URI can't be trace to a MediaSource object. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 12:01:13 +1000 - rev 398985
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: An invalid or revoked MediaSource URI can't be trace to a MediaSource object. r?gerald https://w3c.github.io/media-source/index.html#mediasource-attach: "If the resource fetch algorithm absolute URL matches the MediaSource object URL, ignore any preload attribute of the media element, skip any optional steps for when preload equals none" A dummy URL or a revoked one no longer matches the MediaSource object URL, as such, the preload attribute isn't to be ignored. MozReview-Commit-ID: EW5TOv9SSf
09f3c6e8ea1e6956a0266352aded5ceb5bdd6ae7: Bug 1293613: Correct mediasource-duration.html r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 11:57:32 +1000 - rev 398984
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Correct mediasource-duration.html r?gerald - The WebM file manifest correctly indicates the duration as reported in the metadata. However, the last frame has an end time 0f 6.05s which would adjust the duration. As such it is incorrect to assume that after a full appendBuffer the duration will remain the same as set in the metadata. (source: https://w3c.github.io/media-source/index.html#sourcebuffer-coded-frame-processing "5. If the media segment contains data beyond the current duration, then run the duration change algorithm with new duration set to the maximum of the current duration and the group end timestamp") - When setting the duration, the actual final duration may be different to what was set as it will be aligned to the highest end time (source: https://w3c.github.io/media-source/index.html#duration-change-algorithm ("4.1 Update new duration to the highest end time reported by the buffered attribute across all SourceBuffer objects in sourceBuffers.") MozReview-Commit-ID: EpzSaSg8pWW
c3ee81dc96a50afb0d56fc5cd700817c900bfe09: Bug 1293613: Update manifest with new test scripts. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 11:50:42 +1000 - rev 398983
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Update manifest with new test scripts. r?gerald MozReview-Commit-ID: C8vMTcWiDJ5
a9b4cd9b27d77e6f0174332b5d3cfb5ba3aaca1b: Bug 1293613: Don't assume that all videos start at 0. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 09 Aug 2016 21:40:37 +1000 - rev 398982
Push 25696 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:25:42 +0000
Bug 1293613: Don't assume that all videos start at 0. r?gerald The tests incorrectly assume that all videos start at 0. However this is often not the case, in particular for the mp4 files. The buffered range is the intersection of the audio track and the video track. As such, if the video track starts at a later time than 0, the buffered range of the source buffer can't be starting at 0. Rather than using different videos, we properly use the correct values; this is done to ensure that buffered range are calculated correctly, regardless of the video content. timestamps verify with mkvinfo utility for webm and ffprobe for mp4. See issue https://github.com/w3c/web-platform-tests/issues/1939 MozReview-Commit-ID: AMKgJHEJsWr
68ea8e5784b44beab867f9feba11125b386f89b1: Bug 1293927: Always use MediaSource seekable range regardless of readyState. r?jwwang draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 14:14:37 +1000 - rev 398981
Push 25695 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:24:50 +0000
Bug 1293927: Always use MediaSource seekable range regardless of readyState. r?jwwang MozReview-Commit-ID: 7ae467k5PSf
e43df1921b2dec90e0387843311add1aa228969e: Bug 1293576: [MSE] P2. Fix mochitest. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 16:21:36 +1000 - rev 398980
Push 25694 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:24:12 +0000
Bug 1293576: [MSE] P2. Fix mochitest. r?gerald The mochitest relied that the video track was processed first. Additionally, change for the file with only a single video track as the previous video didn't have aligned segments, making the use of sequence mode useless. We swap the segment around, which allow to more easily visually inspect the result (counter goes forward and then back) MozReview-Commit-ID: 33PsrmRF1GL
604247b6c4a49122c64a2684c0964524843be953: Bug 1293576: [MSE] P1. Always process the earliest frames first when in sequence mode. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 09 Aug 2016 23:11:36 +1000 - rev 398979
Push 25694 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:24:12 +0000
Bug 1293576: [MSE] P1. Always process the earliest frames first when in sequence mode. r?gerald MozReview-Commit-ID: 2b3EyYCtNai
525505cb05a26b558243a27d29379b167363d1b0: Bug 1293646: [MSE] P2. Only reject a seek request with EOS if it's passed the explicit duration. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 10 Aug 2016 15:30:12 +1000 - rev 398978
Push 25693 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:23:34 +0000
Bug 1293646: [MSE] P2. Only reject a seek request with EOS if it's passed the explicit duration. r?gerald With MSE, the actual duration is always exact as it is amended when data is added. We do not want to fire ended when we attempt to seek to unbuffered data once endOfStream has been called. Instead we will fire the waiting event. MozReview-Commit-ID: Cl2uBLk2qRQ
1204c7192c3abd30def828c0773ee9f7e2288706: Bug 1293646: [MSE] P1. Reject seeking attempt with EOS when the mediasource is ended. r?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 09 Aug 2016 23:09:22 +1000 - rev 398977
Push 25693 by bmo:jyavenard@mozilla.com at Wed, 10 Aug 2016 06:23:34 +0000
Bug 1293646: [MSE] P1. Reject seeking attempt with EOS when the mediasource is ended. r?gerald Otherwise, the ended event would never be fired should the decoder have reached the end of the stream prior endOfStream being called. MozReview-Commit-ID: CbWCnzi3nxj
3e6e46e3038c9905ae5dcdd5d1b19488db8f4139: Bug 1290782 - Force using image size as SVG's viewport size when drawing the border amd the SVG doesn't have fixed ratio. r?dholbert draft
Kevin Chen <kechen@mozilla.com> - Tue, 09 Aug 2016 17:17:47 +0800 - rev 398976
Push 25692 by bmo:kechen@mozilla.com at Wed, 10 Aug 2016 05:36:22 +0000
Bug 1290782 - Force using image size as SVG's viewport size when drawing the border amd the SVG doesn't have fixed ratio. r?dholbert MozReview-Commit-ID: LPUAP7xVssu
dbd2f355e325c04b8382af62c7e3e75e62054a87: Bug 1293601 - Show slider and mute button at firt show on video touch control. r?jaws draft
Ray Lin <ralin@mozilla.com> - Wed, 10 Aug 2016 13:18:46 +0800 - rev 398975
Push 25691 by bmo:ralin@mozilla.com at Wed, 10 Aug 2016 05:23:21 +0000
Bug 1293601 - Show slider and mute button at firt show on video touch control. r?jaws MozReview-Commit-ID: E9cilyGDZRK
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip