For webrtc, the most important part of the code had already been removed in bug 1355048 and could no longer be called
MozReview-Commit-ID: Fx9XI0zR1gn
--HG--
extra : rebase_source : 360996760abab650684440fbeea258b43dccfd83
So different test timeouts from the same test case will fall under the same bug.
MozReview-Commit-ID: LDstAhOpkYK
--HG--
extra : rebase_source : 9f2b52f237f18f3fecdd076295da4d43e5b30219
This test stops a stream and checks MediaRecorder events when trying to record it.
However, streams can't be stopped anymore (they go inactive), so there's nothing
left for this test do do.
MozReview-Commit-ID: 3pLlhLzBkNA
--HG--
extra : rebase_source : 7c159fa2be96aa99ca22e0530ee0f79395a00491
extra : source : 038e8eecd3dd50bcc1e50d5e41f8266e3ace0c39
In patch3, we remove the minimum resolution check, now the video under 48x48 can
be playback successfully. Therefore, removing them from error test and we should
ensure they can be playback.
MozReview-Commit-ID: BvLtr4DN1hU
--HG--
extra : rebase_source : 30b9dc35f5754d6ecc7cddaf7f5a9fabf9965889
In patch3, we remove the minimum resolution check, now the video under 48x48 can
be playback successfully. Therefore, removing them from error test and we should
ensure they can be playback.
MozReview-Commit-ID: BvLtr4DN1hU
--HG--
extra : rebase_source : 36cdd1e18cd41516319989b56e4e83888b0ecf50
The MediaRecorder should now transition to inactive immediately upon an error
being encountered. This contrasts with the previous behaviour where onerror
would be called before performing this transition. This changeset updates
tests to reflect this new behaviour.
MozReview-Commit-ID: 5V2JkoMb0wB
--HG--
extra : rebase_source : cdd61c7fe128089458fd93f18d6b133a52b9b8aa
Since the street.mp4 is a fragment mp4, the duraion is unstable when seeking in the testcase, change the test file to gizmo.mp4.
MozReview-Commit-ID: 8eQ9tfKwxZF
--HG--
extra : rebase_source : a15dfd0994456809241f9dd5a0c44239beda4e16
* test_playback_rate.html
In the patch2, we would honestly return the value of playback rate.
* test_info_leak.html/test_load.html
According to [1], we should only dispatch event "ratechange" when playbackRate or
defaultPlaybackRate attribute has just been updated. In these tests, they didn't
change the playbackRate or defaultPlaybackRate, we should not expect for the
"ratechange" event.
[1] https://html.spec.whatwg.org/multipage/media.html#event-media-ratechange
MozReview-Commit-ID: LjVDNnf4YX4
--HG--
extra : rebase_source : 3b58649212c24ccd5e17a64c3dc7fce8a9600207
It isn't possible for the End of Stream algorithm to cause an updateend event to fire. Regardless of the duration being modified.
MozReview-Commit-ID: 5RppbtjkboN
--HG--
extra : rebase_source : 6d30be7758bda59c545324358c82c47e6b0c73b1
We load 10s of encrypted video, which should trigger readyState being HAVE_ENOUGH_DATA
MozReview-Commit-ID: 4VRLFHSFlDs
--HG--
extra : rebase_source : 919310b00f0ec271a73e149992696bc1eec8cd5f
Change where load calls are used in media recorder principals test to more
reliably force cross origin requests.
MozReview-Commit-ID: 7La6ZIRmsTQ
--HG--
extra : rebase_source : 58b8049de46ad5800300033dd4ee101e68171c70
Update the MediaRecorder principal test to behave more like
test_mixed_principals.html. This involves preloading metadata and using a
longer video to test with. This particular combination currently results in
multiple requests being made for the resource, however this is not a robust
solution in that the behaviour of the MediaCache and associated objects may
change and break this. This fixes the issue for now as best I can tell, but
a follow up gtest or may be a more sensible long term solution.
MozReview-Commit-ID: F9gnnzGt3Cu
--HG--
extra : rebase_source : 8444f135033fbed350266ebfe5faafc245ff5596
MediaRecorderErrorEvent is now fired in response to async errors in the
MediaRecorder. This event wraps a DOMException and tests need to be updated to
reflect this new behaviour.
MozReview-Commit-ID: JIjIZlJJ8PE
--HG--
extra : rebase_source : b8adde26f5321b5b8a3c8e193c5744d6f3403cf5
MediaRecorderErrorEvent is now fired in response to async errors in the
MediaRecorder. This event wraps a DOMException and tests need to be updated to
reflect this new behaviour.
MozReview-Commit-ID: JIjIZlJJ8PE
--HG--
extra : rebase_source : f9667b8a1b2a82959624831f3ef5109c19fccbd6
This patch modifies the test case 'test_video_stats_resistfingerprinting.html'
to check media statistics report spoofed values when fingerprinting resistance
is enabled.
This test will play a video and test the media statistics when the video is finished.
It will make sure all media statistics report correct spoofed values corresponding
to the play time of the video.
MozReview-Commit-ID: GpYewu7cIbY
--HG--
extra : rebase_source : 0eb771c4a9472436f990d53a042656a60bab22f6
The original duration I wrote is calculated from the m3u8 file this is too accurate without error tolerant.
The state machine will update playback position periodically(UpdatePlaybackPositionPeriodically)
according to the clockTime or max end time from A/Vsink.
So the duration will be variant that I should consider to set the value to a more relaxed value.
MozReview-Commit-ID: GGwkhvzz8sI
--HG--
extra : rebase_source : c0465f7aef7a41e999e8c4c3429957fa56336239
bechen@mozilla.com
Jean-Yves Avenard
Tyson Smith
Paul Adenot
Bob Clary
Jesse Ruderman
Ethan Lin
Ryan VanderMeulen
Joel Maher
Kartikaya Gupta
JW Wang
Andreas Pehrson
Alastor Wu
Sebastian Hengst
James Cheng
Bryce Van Dyk
Alfredo.Yang
Wes Kocher
Tim Huang