2022-06-16: Added DisplayMediaStreamConstraints.surfaceSwitching to the list of changes this TAG review is for.

Hello Elad @eladalon1983,

We have a discussion in our TAG breakout B meeting, we currently have the following comments:

1. Could you please elaborate more on the multi-stakeholders support of those proposed features?
2. Please do not use google docs for the explainers. You can refer to https://tag.w3.org/explainers/ for explainer writing.

Since there is no response for the comments for a while, close this for now. Please re-open it when necessary.

Apologies for not responding earlier. I am on extended PTO at the moment and so I try to limit work to keeping-the-lights-on.

1. Could you please elaborate more on the multi-stakeholders support of those proposed features?

1. Yes.
   • Each of these mini-features links a PR that was merged with the approval of one Mozilla rep and one Apple rep.
   • The linked ChromeStatus entries each reference a request for an official position from Mozilla and Apple. As of the time of this writing, not all of these have received an official response.

2. Please do not use google docs for the explainers. You can refer to https://tag.w3.org/explainers/ for explainer writing.

2. I will migrate the explainers and @mention you (@maxpassion) with a request to reopen this thread. This will likely happen in about a month.

Hi @maxpassion. The explainers are now also available in .md form here:

• DisplayMediaStreamConstraints.selfBrowserSurface explainer
• DisplayMediaStreamConstraints.surfaceSwitching explainer
• DisplayMediaStreamConstraints.systemAudio explainer
• MediaTrackSupportedConstraints.suppressLocalAudioPlayback explainer
• displaySurface Constraint explainer

Could you please re-open this issue and review?

Hi @eladalon1983 thank you for providing the .md versions of the documents. As we attempt another review today, we found it difficult to understand what is the overall ask for this design review.

In this linked thread it was already suggested that you combine the review and outline what are the goals and non-goals, what was considered as alternative approaches, and what should the TAG focus on reviewing - PRs, parts of the PRs etc. If nothing else, at least you can capture these in the issue here.

The request is for a review of the five new API surfaces introduced by the five PRs referenced in the original post in this thread. Each PR is associated with its own explainer, linked in the original post on this thread; now also on .md form as per TAG's request. Each of these five surfaces is completely distinct and can be reviewed independently. However, they are presented together here so as to help form a cohesive general picture.

With respect to alternatives considered - each surface had its associated discussion in the WebRTC WG. Some discussions were captured in their respective GitHub discussions.

When triaging this request and attempting to set a priority for it, it might help you to know that, in the intervening time since this thread was started in 2022-06-02, Chrome has already shipped all of these surfaces.

Thank you for taking the time to revisit this, and we apologize for the delay on our end. We've discussed this at length in our virtual F2F, and not only do we think these are useful features for the platform, but we have seen how it was useful in the wild (especially given the pandemic) and we're happy to see features like this make the platform more capable to the users.

Thank you for bringing this to our attention!