- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Jun 2023 17:23:19 +0000
- To: public-webrtc-logs@w3.org
> How do we make this work with the UI such that the user can easily understand what is going on? This concern was raised by Tim (@steely-glint). While I think that Colin's (@Coread) proposal is reasonable, there's no way for us as spec authors to decide that for any implementation. I think that we need to take a step back and discuss whether UX is even a reasonable question to debate. Specs levy certain requirements on UX. For example, our spec mandates: > For the newly created MediaStreamTrack, the user agent MUST NOT capture the prompt that was shown to the user. So I acknowledge that UX is somewhat within the realm of specs, but I don't think the concern Tim raised falls within that realm. * If a developer is concerned that the UX employed by a browser is confusing, then that developer can avoid invoking the new API and file a bug. * If a browser implementer is unable to come up with what **they** believe is a reasonable UX, they are free to not implement this preference, which is intentionally structured as an optional hint, as was [selfBrowserSurface](https://w3c.github.io/mediacapture-screen-share/#dom-displaymediastreamoptions-selfbrowsersurface). --- @jan-ivar, you raised the question of default value. I think we should specify it as `"include"`, which is the default behavior on all existing implementations. I'd also be open to not specifying a default, as we have done with a few similar preferences. --- @youennf, you raised the question of dynamic switching in macOS. I think it'll be beneficial for Safari to have the **flexibility** to block dynamic switching from a window to a screen if the app requests that. But you're not compelled to, as this is a preference/hint. Wdyt? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/261#issuecomment-1609936218 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 June 2023 17:23:21 UTC