W3C home > Mailing lists > Public > public-media-capture@w3.org > January 2016

Re: [mediacapture-main] getUserMedia: spec does not define what happens when browser gUM dialog disappears completely

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 12 Jan 2016 11:50:21 +1100
Message-ID: <CABkgnnVO1q=eCE6C5cazyc+kZehe4pLJhKCBc2sZ97auKyCtFg@mail.gmail.com>
To: jnoring via GitHub <sysbot+gh@w3.org>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
This is a UX issue, and not one for the spec.

Note also that Firefox doesn't cause the dialog to disappear
completely, it becomes minimized instead.

On 12 January 2016 at 04:37, jnoring via GitHub <sysbot+gh@w3.org> wrote:
> jnoring has just created a new issue for
> https://github.com/w3c/mediacapture-main:
>
> == getUserMedia: spec does not define what happens when browser gUM
> dialog disappears completely ==
> Currently, some browsers--namely Firefox--will remove the gUM prompt
> if a browser swaps to a different tab, or goes to another application.
>   The problem is the page receives no notification about this dialog
> going away, so processing in the page is generally hung waiting for a
> success/error promise or callback to fire.
>
> The current spec doesn't appear to address this (I could be wrong
> about this). If the gUM prompt goes away for any reason without user
> interaction, should the calling page be informed of this?
>
> Please view or discuss this issue at
> https://github.com/w3c/mediacapture-main/issues/303 using your GitHub
> account
>
Received on Tuesday, 12 January 2016 00:50:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:35 UTC