- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Sep 2020 19:59:51 +0000
- To: public-webrtc-logs@w3.org
> The upsides of the change: > > * a perceived "privacy enhancement" around capture indicators No. The upsides are noticeable privacy enhancements that have been positively welcomed by privacy experts. See https://github.com/w3c/mediacapture-main/issues/709#issuecomment-686409911 for some benefits. A behavior change is always painful and it is much easier to adapt to the change if you know why it was done. I am happy to continue discussing and describing these benefits. > But our discussion shows this change cannot be realised in practice. I do not know how the discussion shows this. This change is implemented and the benefits have been realised. > The downsides: > > * change in API behaviour affects existing code in the wild True. As I said above, I am more than happy to help mitigating the pain of migrating to the new behavior. There is a proposed API usage pattern to ease migration. AFAIK, this pattern works with all major browsers, implementing the change or not. > * the new behaviour is unusual and not straightforward (I am not the only person already asking for clarification) This is a subjective statement. > * the new behaviour is not efficient (examples given require multiple device opens to workaround new behaviour) I haven't seen any proof the new behavior is less efficient. As asked previously, please provide precise examples to demonstrate this claim. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/709#issuecomment-687353052 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 September 2020 19:59:53 UTC