- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Sep 2022 07:40:05 +0000
- To: public-webrtc-logs@w3.org
It seems we have two paths here. 1. focus() is a one time thing. This option is more capturer saying "I made a decision to focus or not to focus". In that case, I would prefer that web site be explicit about either 'I focus' or 'I do not focus'. 2. focus() is a way to focus capturee, not just after getDisplayMedia but at any point in time. It does not seem bad for capturer to provide UI to quickly go to capturee. In that case, we could gate it by standard user activation, and we could say that getDisplayMedia prompt selection (if successful) is a user activation. AIUI, current proposal is close to 2 but with the constraint that focus() is called only once around the time getDisplayMedia is called/resolved. > I think this would defeat use cases such as screen recording. My working assumption [as presented](https://docs.google.com/presentation/d/1ulgTHkHcpUa7FBtPHYYsUL1ATjO1meRmW5ghB9ELDXg/edit#slide=id.g12b1145f5f6_9_123) has been that screen-capture isn't solely a tool for video conference presentations My understanding was that it is difficult to predict what VC apps want. For screen recording applications, isn't it the case that they will always want one or the other, irrespective of the selected surface, something like: - Always focus if starting to record right away - Do not focus at getDisplayMediaTime. Try to focus when user presses the record button (which will probably happen a few seconds after getDisplayMedia resolution time). > I also agree that previews are the solution to mis-selection. This is not sufficient. An attacker can make two pages looking exactly the same (previews will not help there) and get to a point where capturer is capturing a surface that it can navigate while continuing to capture. Unfocusing makes this attack a little bit easier (attacker will no longer need to trick user in unfocusing the capturee). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/230#issuecomment-1235174888 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 September 2022 07:40:07 UTC