Re: [mediacapture-screen-share] Bring back constraints for downscaling, not selection filtering. (#49)

> For security reasons, in getDisplayMedia the user is given control over selection; constraints do not influence selection, but rather, characteristics of what is selected (e.g. resolution, framerate, etc.)
> […](#)
> On Tue, Jun 5, 2018 at 1:49 AM Maria Fernandez ***@***.***> wrote: Hey! Not sure if this belongs here, but I think so, as the discussion goes about what constraints will getDisplayMedia accept. I am now playing a bit with the implementation of that method that Edge just released quite recently. When using getDisplayMedia the user can either select to share a window (application) or the whole display. I was wondering if there is any chance this would be customizable through constraints (i.e. limit the sources a user would be able to select for sharing to only the whole desktop or only application windows). This can be done in Chrome with mediaSource constraint. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <[#49 (comment)](https://github.com/w3c/mediacapture-screen-share/issues/49#issuecomment-394632199)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAxXa6JpuFqt1ELjZofl8zVrcZ2zxP8fks5t5kY0gaJpZM4PT73k> .

I think the option to deny the user to select a specific tab or application to share is crucial for security reason. I mean, I'm integrating a webrtc app for a bank, and the boss is worried that the operator can share for mistake the entire screen instead of a tab and send the customer sensible data while doing that.

This is a case to consider to me, or the getSettings() should also return the title of the tab shared, not only "window" or "screen", so we can stop the screensharing if the tab is "blacklisted".

Do you have any suggestion to how implement this with the actual state of APIs?

-- 
GitHub Notification of comment by kekkokk
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/49#issuecomment-469167851 using your GitHub account

Received on Monday, 4 March 2019 08:49:59 UTC