[mediacapture-screen-share] Distinct error type for explicit user rejection (#321)

eladalon1983 has just created a new issue for https://github.com/w3c/mediacapture-screen-share:

== Distinct error type for explicit user rejection ==
When getDisplayMedia() is called, a browser-level prompt is shown. To serve their users better, Web applications need to know if users rejected that prompt explicitly, or if the UA rejected the call on the users' behalf.

**On the one hand**, if the **user** rejected the prompt, the Web application should take no further action. Some possible reasons for the user to do this include:
- The user clicked the wrong button in the Web app itself.
- The user changed their mind last moment (e.g. if another participant started presenting a moment ahead of them).

Whatever the reason, it's best for the Web app to AVOID explaining to the user that "you have not granted permission to share the screen."

**On the other hand**, if the **UA** auto-rejected the prompt, and the user never even saw a prompt, the user is going to be confused if nothing happens in response to their click. The Web application is compelled to step in and explain to the user what has just happened, e.g. with a message that says "no permission to screen-share; click here for a list of possible reasons."

To ensure that such messaging is only delivered when it is relevant, Web applications need a way to distinguish explicit user rejection from other reasons. Users benefit from the apps' increased ability to serve them.

With respect to the exact solution – I am not picky. I propose that we could specify a subclass, as we did with [OverconstrainedError](https://www.w3.org/TR/mediacapture-streams/#overconstrainederror-interface). We could for instance have a `NotAllowedByUser` interface. But I am open to other approaches, so long as they solve the core issue.

Wdyt? (CC @youenf, @jan-ivar)

Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/321 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 8 May 2025 09:17:18 UTC