- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Mar 2021 16:35:58 +0000
- To: public-webrtc-logs@w3.org
> If you can help me find a variation that satisfies everyone¹, or that can be an acceptable compromise for everyone, I would be very grateful. @eladalon1983 I showed how this customer can accomplish their workflow with a few lines of JS, and how browsers that want to can detect and optimize the UX flow in that case, even though we don't recommend it. Can you help me understand why they'd need this behavior standardized for all apps? As to browser UX, specs have a hard time mandating it. Where strong recommendations have had teeth in the past, they're paired with good privacy or security arguments, to convince (or shame) implementers with. So proposing a parameter to induce UX (going _against_ strong privacy recommendaetions) seems like a dead-end. > We should gate gvp on transient activation like done for gdm @youennf Agreed, among a [list of other things](https://docs.google.com/presentation/d/1CeNeno5XuDhm1mpnVyE9eT14YKZgZUtgQsJfC8uqEpA/edit#slide=id.gaef31c926d_1_111). > if gvp fails, transient activation stays valid in the reject handler so that gdm can be called right after [Transient activation](https://html.spec.whatwg.org/multipage/interaction.html#transient-activation) is time-based, so we may not need to say anything about it since gvp would fail immediately. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/pull/148#issuecomment-808358950 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 March 2021 16:37:43 UTC