New issue
Advanced search Search tips

Issue 645958 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 721412
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature



Sign in to add a comment

DevicesNotFoundError should contain a non-empty error message

Project Member Reported by oseg@chromium.org, Sep 12 2016

Issue description

Version: 53.0.2785.101 (64-bit)
OS: Ubuntu 14.04 LTS

What steps will reproduce the problem?
(1) Use navigator.webkitGetUserMedia with constraints to request a missing video device, e.g. { video: { mandatory: { sourceId: 'foo' } } }.

What is the expected output?
NavigatorUserMediaError {name: "DevicesNotFoundError", message: "No such video input device 'foo'", constraintName: ""}

What do you see instead?
NavigatorUserMediaError {name: "DevicesNotFoundError", message: "", constraintName: ""}

In cases where both specific audio and video are requested it becomes difficult to determine which of the devices that couldn't be found.

The sane applies to ChromeOS.
 

Comment 1 by mcasas@chromium.org, Sep 26 2016

Components: Blink>MediaStream
Labels: -OS-Linux -OS-Chrome OS-All
oseg@, navigator.{webkitG,g}etUserMedia() are in the process of
being deprecated in favour of navigator.MediaDevices.getUserMedia()
(promise-based) [1], does this new method also have an meaningless
error message? 

Also it'd be great if you could point to the DOMException you'd
expect to see out of those in [2].


[1] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/qUOfAge9qnk
[2] https://www.w3.org/TR/mediacapture-streams/#dom-mediadevices-getusermedia

Comment 2 by mcasas@chromium.org, Sep 26 2016

Labels: Needs-Feedback

Comment 3 by oseg@google.com, Sep 28 2016

Calling
    navigator.mediaDevices.getUserMedia({ audio: { mandatory: { sourceId: 'foo' } } })
yields
    NavigatorUserMediaError {name: "DevicesNotFoundError", message: "", constraintName: ""}
The error is the same as in my example.

However,
    navigator.mediaDevices.getUserMedia({ audio: { mandatory: { deviceId: 'foo' } } })
yields the much more understandable
    NavigatorUserMediaError {name: "ConstraintNotSatisfiedError", message: "Unknown name of constraint detected", constraintName: "deviceId"}

I expect the error message in the first example to be as detailed as in the second example.


Comment 4 by mcasas@chromium.org, Sep 28 2016

Cc: guidou@chromium.org hta@chromium.org
guidou@ can you take a look please?

Comment 5 by mcasas@chromium.org, Oct 17 2016

Owner: hta@chromium.org
Status: Assigned (was: Untriaged)
hta@ please triage or assign this issue, thanks!

Comment 6 by hta@chromium.org, Apr 5 2017

Owner: guidou@chromium.org

Comment 7 by guidou@chromium.org, Oct 16 2017

Owner: orphis@chromium.org

Comment 8 by guidou@chromium.org, Oct 16 2017

Mergedinto: 721412
Status: Duplicate (was: Assigned)

Sign in to add a comment