#892: DisplayMediaStreamOptions monitorTypeSurfaces

Visit on Github.

Opened Sep 1, 2023

こんにちは TAG-さん!

I'm requesting a TAG review of DisplayMediaStreamOptions monitorTypeSurfaces.

When getDisplayMedia() is called, the browser offers the user a choice of display surfaces: tabs, windows, or monitors. Using the monitorTypeSurfaces option, the web application may now hint to the browser if it prefers to include display surfaces whose type is monitor among the choices offered to the user. The browser may still ignore this hint. Web applications are therefore encouraged to still check the displaySurface setting of the tracks they receive.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: N/A
  • The group where the work on this specification is currently being done: W3C WebRTC Working Group
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): W3C WebRTC Working Group
  • Major unresolved issues with or opposition to this specification: N/A
  • This work is being funded by: Google

You should also know that this feature is a simple addition of a single flag to an existing dictionary, following an established pattern that’s also used by a few other keys of the same dictionary (selfBrowserSurface, systemAudio, surfaceSwitching). well-known patterns. We already filed a TAG review for similar options at https://github.com/w3ctag/design-reviews/issues/744 which was marked as satisfied.

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 @beaufortfrancois @eladalon1983

Discussions

Discussed Jan 1, 2024 (See Github)

discussion about accessibility and privacy/security implications

Sangwhan: this seems fine to me

Martin: I see no major issues

Yves: ...

Martin: what is seen is what is shared

Sangwhan: if you wanted to exfiltrate informaton you could run an ocr engine on the other end... orthogonal. It's an optional feature for browsers, can just ignore it.

Martin: pop something up from another website which password manager autofills and they don't use password masking, so you can grab the password

Sangwhan: writes closing comment

Discussed Jan 1, 2024 (See Github)

Dan: Should have been closed before. closed

Comment by @cynthia Jan 23, 2024 (See Github)

Discussed this (w/ @martinthomson @rhiaro and @ylafon) during F2F. We discussed the potential security/privacy implications of this, in particular whether there are ways to steer users in a direction that allows extraction of information and there is low (to zero) risk. We're happy to see this move forward.

Comment by @beaufortfrancois Jan 23, 2024 (See Github)

Thank you @cynthia!