Re: [mediacapture-screen-share] Avoid Hall-of-Mirrors (#209)

To echo @martinthomson, I'm OK with this idea.

My long-view is [getViewportMedia]( is for self-capture, and [getDisplayMedia]( is for everything else. So anything that weans users off of expecting the current tab in the picker early seems good.

@jesup I agree there's no security improvement here. While I'm slightly concerned this change might lull users into not expecting the current tab to be in the picker ever, turning this into a marginal social engineering advantage for a malicious site (e.g. "See, the browser even has special rules for us asking you this"), I don't think it outweighs the benefits.

  boolean excludeCurrentTab = ?;  // Default value - let's discuss.
I'd like `= true`, based on where we'd like to end up.

But to follow the [TAG's "see also" design principle:]( ["APIs that have boolean arguments defaulting to true"]( it'd have to be:
  boolean includeCurrentTab = false;

> ... some legitimate applications currently use self-capture, and some existing browser would be apprehensive of breaking them (e.g. Chrome).

Do you have a list of these apps? If it's from [here](, they should be unaffected.

Anecdotally based on every video meeting I've been in, capture of other tabs dwarfs self-capture. So without further data, I'd guess the few apps that rely on socially engineering their users to select a specific choice in the picker, are industrious enough to add `includeCurrentTab: true` to keep their apps working.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 10 March 2022 22:29:34 UTC