#856: API for capturing all screens
Discussions
2023-06-19
Dan: Do we need this in the web platform itself? isn't his better put at the system level? Why does this need to be in a browser API?
Sangwhan: Proctored exams (monitored exams), monitoring employee productivity, call centers...
Amy: it says it's behind an enterprise policy - we've pushed back before on this kind of surveillance in the web platform ... eg. managed device API
Hadley: aren't enterprise policies usually at the OS level?
Dan: we said fine if they want to add it to Chrome as their own thing, but maybe not appropriate for standardisation
Sangwhan: jist is that the proctored test is usually a web application - on the web. You'd either have to make a native application to do the same thing - which is what is going on right now - this moves some of that horrible stuff to the web. I can see who wants to use it and why it makes sense... You can give the user a capture that this is being captured... User permission requested. In the browser. In native code, all bets are off. In that sense I think it's better than being in native.
Amy: they don't list exams as one of their use cases...
Hadley: I'm hesitant to respond to a use case they haven't made explicit.
Yves: if it's an enterprise based installation, they can probably install a native extension to chrome that may be needed for the same thing. Dangerous to have that avalable for everyone on the web.
Amy: they don't go into detail about the end user needs, just high level summary use cases
Sangwhan to leave a comment
2023-07-17
Amy: feedback before is that this is an enterprise thing ... maybe not in the web platform? Their response assumes an extension is untrustworthy, but I don't understand, as in this situation wouldn't they be the ones providing the extension?
Yves: if you know that the enterprise is putting extensions on you then you know what to expect - if it's part of the web platform in general then you don't.
Amy: ... APIs the admin might not know about.. isn't it the duty of the admin of an enterprise system to know about what they're telling their users to install/use?
Dan: ... safe to browse...
Dan: leaves comment
2023-07-mos-eisley
reviewing the comments from Elad
Amy: the fact that it's constrained by admin allowlist suggets it needn't be on the web
Dan: like managed device api
Sangwhan: if another implmeenter is interested, they could converge and figure it out and maybe there's a path to standardisation. But probably recommend we say it's not part of the web
Dan: we said unsatisfied on managed device because of the use cases - not in users best interests, contravenes best interests of the user. Reasonable for us to give the same view. Unsatisfied. Adding as a configuration option on enterprise deployments for chrome, that's their business.
Amy: +1
Dan: we can reinforce the user can't "just walk away", and making these policies harder to implement differentiates the web platform from other platforms close and comment
OpenedJun 12, 2023
こんにちは TAG-さん!
I'm requesting a TAG review of "capture all screens" (getAllScreensMedia).
In some scenarios (e.g. legal compliance or training purposes) it must be ensured that all screens attached to a client are captured. With
getDisplayMedia, a web application would need to call the API N-times, asking the user to pick a different screen each time. This is a cumbersome and error-prone process and it can't be guaranteed that all the screens are captured. We propose thegetAllScreensMediaAPI that allows capturing of all screens without user interaction. To protect the users privacy, the API is safe-guarded by an enterprise policy and the user must be notified before capture can happen and while capturing is happening.Further details:
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify @shangl