- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Mar 2020 21:59:34 +0000
- To: public-webrtc-logs@w3.org
That seems backwards to me, when [that doc](https://wicg.github.io/page-lifecycle/#unfrozen) [refers back to webrtc](https://docs.google.com/document/d/1QJpuBTdllLVflMJSov0tlFX3e3yfSfd_-al2IBavbQM/edit) as a heuristic **_not_** to freeze. IMHO we can define the behaviors we want irrespective of exposure of some new JS API. We seem to be mixing things. To recap observations in this thread: 1. Closing a laptop lid is _**not**_ the same as freezing. It may _trigger_ it, but was observed not to. 2. It's a physical act that (sans external display) seizes display, audio output, mic & cam capture. 3. It should have no direct impact on a peer connection. So what happens to the peer connection when the laptop lid closes? Nothing. What happens to the peer connection when the page suspends? Please open a new issue. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2489#issuecomment-602879082 using your GitHub account
Received on Monday, 23 March 2020 21:59:35 UTC