- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Mar 2020 09:50:21 +0000
- To: public-webrtc-logs@w3.org
To me it seems that: 1) the event we're looking for seems to be the "change the frozenness" event, triggered at https://wicg.github.io/page-lifecycle/#frozenness-state 2) when frozenness changes to frozen, it makes sense to mute all tracks with device sources (mediacapture-main); when frozenness changes to unfrozen, it makes sense to require some specific action (page in front? user interaction?) before unmuting. 3) there is no chance for JS to gain control between frozen and discarded state. 4) when returning to a discarded context, there will be a "discarded" boolean - but I don't think anything else from the previous context survives? We shouldn't specify anything here, I think. What else? -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/668#issuecomment-601614212 using your GitHub account
Received on Friday, 20 March 2020 09:50:22 UTC