- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jan 2022 15:30:49 +0000
- To: public-webrtc-logs@w3.org
> > Suppose an application cares about when a Promise is zombified.
>
> Can you clarify why applications would actually care about this?
Consider an application that records an employee, either for compliance reasons, for quality assurance, or for billing. The application issues local and/or remote alerts if unable to record for N minutes. It helps to have a dedicated error for the Promise timing out while backgrounded, so that the local user could be appropriately informed of what went wrong. ("You have already approved mic+camera permissions, but we still need you to focus this tab to start recording.") Locally presented information would still be presented only on-focus-regain, so rejecting in the background is not strictly necessary (assuming dedicated error). For informing a remote controller, likely an application-specific timer would be employed. For telemetry and debuggability, it would be nice to also know if a UA-timer has elapsed, but I guess that's not strictly required. So maybe the minimum required change here would be to say that a UA timing a gUM has to fire a specific unique error.
--
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/846#issuecomment-1008996699 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 January 2022 15:30:51 UTC