- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Mar 2022 18:09:43 +0000
- To: public-webrtc-logs@w3.org
> This does not prohibit User Agents to optimise their pickers based on that property. Your suggestion makes sense to me up to this point. :-) I see two issues: 1. Obfuscating some region and changing pickers - these are mostly orthogonal issues. Why should the UA infer one from the other? That's a compat issue. What will an application that expects anything-but-current-tab do when it gets current-tab-but-obfuscated? 2. Implementing obfuscation will take time, and AFAICT is not on anyone's agenda. (Not on Chrome's agenda at any rate. Let me know if it is on yours.) What will we do until obfuscation is implemented? Not expose its control, and therefore not infer anything in the picker? Expose it and make it no-op for its stated-purpose of obfuscation, but use it for inference? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1060978875 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 March 2022 18:09:45 UTC