W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2019

Re: [mediacapture-record] Shouldn't remaining async methods run "in parallel"? (#131)

From: Andreas Pehrson via GitHub <sysbot+gh@w3.org>
Date: Tue, 22 Oct 2019 09:12:30 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-544872905-1571735549-sysbot+gh@w3.org>
It turns out implementations are not starting and stopping the gathering of data in the queued tasks per the spec's current language, but doing it immediately. At least for `pause()` and `resume()` which the issue mentions. Only the firing of the event is done in the queued task. This is true in [Firefox 70](https://searchfox.org/mozilla-central/rev/24e87cb986497b5c54610ebfe2b29ab01f7841d6/dom/media/MediaRecorder.cpp#1316) (and earlier) and Chrome 77 (assuming it hasn't change since then until chromium's master branch [as of today](https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/mediarecorder/media_recorder.cc?type=cs&q=MediaRecorder::Pause&sq=package:chromium&g=0&l=282)).

These are in the end done on a background thread, so depending on the definition of "{start|stop} gathering data" current implementations are either doing it synchronously in the algorithm, or "in parallel".

GitHub Notification of comment by Pehrsons
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/131#issuecomment-544872905 using your GitHub account
Received on Tuesday, 22 October 2019 09:12:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:29 UTC