- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Apr 2021 23:53:55 +0000
- To: public-webrtc-logs@w3.org
> what about user state leaked in other ways, such as form controls or `:visited`? What's the story for that? The plan is to rely on permission prompting and privacy indicators, and a list of other items [here](https://docs.google.com/presentation/d/1CeNeno5XuDhm1mpnVyE9eT14YKZgZUtgQsJfC8uqEpA/edit?ts=5fc7fcd2#slide=id.gaef31c926d_1_111) — Any kind of sanitizing risks creating an ad-blocker blocker mode. There's some pushback on the visibility requirement, since there are use cases of capturing e.g. a Google slides presentation in another open tab, without leaving the Google Meet tab, and basically remote-control the presentation with "next page", "previous page" commands out of band from there. Both Chrome and Firefox (behind a pref) support capture of tabs that are in the background today FWIW. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/155#issuecomment-827212860 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 April 2021 23:53:57 UTC