- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Nov 2024 10:18:58 +0000
- To: public-webrtc-logs@w3.org
> I don't find the use cases compelling. Generally, I also don't have use cases in mind at the moment, but I'd love for us to phrase the spec in a way that would not constrain Safari from offering functionality they believe in. Hence my suggestion of SHOULD. I do have one compelling, semi-adjacent use case, though - that of knowing when the app is capturing the current tab. At the moment, this is possible, but requires non-trivial work; see [explanation](https://github.com/w3c/mediacapture-handle/blob/main/identity/explainer.md#use-case-2-avoiding-hall-of-mirrors) for the explanation and [demo](https://w3c.github.io/mediacapture-handle/identity/demos/self_capture_detection/index.html). Possibly we could specify that self-capture (the app capturing its own tab) is exposed via a unique ID that's pre-specified? > This seems to invite applications to make mistaken assumptions. That's a valid concern, but I am not sure if it's significant one - Web developers are competent enough to either use the information correctly, or to **knowingly** choose to employ it as a heuristic, despite its failures. (I find as more convincing the question of whether any Web developer needs this.) -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/308#issuecomment-2475955112 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 November 2024 10:18:59 UTC