- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Sep 2020 17:13:51 +0000
- To: public-webrtc-logs@w3.org
@danjenkins > Ultimately this shouldn't be a userland addition. This should be a browser feature. Do you really trust browser implementations to that degree? I do not. It took 2 years just to convey the reality that Chromium was consistently crashing when variable pixel dimension frames were decoded. Re the arbitrary restriction on Picture-In-Picture window implemented by Chromium, see this response https://github.com/w3c/picture-in-picture/pull/186#issuecomment-646155752 > @guest271314 please stop asking the same question over and over again because you do not like the answer. > > This language is a spec RECOMMENDATION which is in no way a requirement but a suggestion. This suggestion comes from the experience of platforms and browsers implementing Picture-in-Picture (either the Web API or another sort). If a browser implementing this API wants to do something else, it's fully up to them. > Lets say I only want to share the top half of my vertical monitor. I have something private and confidential on the bottom half that I haven't moved off it - there's no way I'm giving say Google Meet access to my entire screen, would I trust that application to not be sending that data somewhere? Process the frames for yourself to ensure you are only exposing what you expect. Again, the PR that fixes exposure of prompt (potentially including windows, applications not intended to be captured) at first frame is not fixed in Chromium source code. > What you're describing above feels like a hack around a solution - and I'm not even certain if its really fulfils the solution to the problem - what if I don't have the browser foregrounded at all. Well, that is all we have right now. Feel free to create a repository specifically for what your goal is and will help where able. > I'm showing off VsCode and another browser different to the one running the meeting application I'm sharing my screen with.... Would explore using "Application" capture at Chromium. > In the web world we stop HTTPS pages being able to talk to HTTP APIs for a reason.... There are various way to get around that limitation, e.g., https://gist.github.com/guest271314/04a539c00926e15905b86d05138c113c. > how is this any different? You want the user to know the web application truly only has access to the portion of the screen I allowed it access to. Also, the above solutions only work if developers implement the ability to do it - shouldn't it be a browser GUM "thing" so that any web application taking advantage of getDisplayMedia is able to use it? Agree that the specification _could_ solve the problem, though the issue was closed. Thus, here, Fix WontFix on own, without waiting for anyone else. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/105#issuecomment-699048648 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 25 September 2020 17:13:53 UTC