- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Sat, 17 Nov 2018 16:03:29 +0000
- To: public-webrtc-logs@w3.org
This was discussed during this week call. This proposal has some drawbacks. This could be ok with tab sharing but what about screen sharing, and the browser tab moving from one screen to another that is shared/not shared. Also this would allow any page to observe what another page is doing which might have bad privacy/security side effects. There is a potential racing issue between this event and actual screen capture, which might make it a bit more difficult to implement correctly. I think the use case would be better served with something like a css property whose purpose would be to obfuscate a field when screen capture is happening. Not sure how simple this would be to implement. Again, ideally it should probably not be observable from the page using this property. Such behavior might be useful by default for some fields like passwords One question is whether the use case would benefit for some chrome UI to unobfuscate specific fields? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/83#issuecomment-439627600 using your GitHub account
Received on Saturday, 17 November 2018 16:03:30 UTC