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

> Or are you saying excludeCurrentTab would forbid user selection of some surfaces? That would be a big change of doctrine.

That is exactly what I am saying. :-) [My original message](https://github.com/w3c/mediacapture-screen-share/issues/209#issue-1147287233) in this thread acknowledged the prior discussions in this vein, and explained why I believe I have new things to say on this matter, and why `excludeCurrentTab` is potentially different. Could you please re-read that message?

> Obfuscation is solving Hall-Of-Mirrors

I disagree. When doing whole-screen-capture, obfuscation helps with Hall of Mirrors. But it's **not at all useful** for tab-capture, because in that case, **the entire track** would be obfuscated.

> Applications will need to deal with this even with excludeCurrentTab, say if selecting a window or screen.

Sorry, but I don't think that is relevant to [my message](https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1060978875). The hypothetical application I was discussing there, would have been ready to handle {any-tab-other-than-the-current-one, any-window, any-screen}. If you think that is unlikely, simply consider an application that stops() the track if `displaySurface` is `!= 'browser'`. The compat issue arises when Chrome follows your suggestion and returns anything-but-current-tab, while Safari can still return the current tab.



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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 8 March 2022 19:08:25 UTC