Deprecate navigator.mozGetUserMedia()
Categories
(Core :: WebRTC: Audio/Video, task, P5)
Tracking
()
People
(Reporter: jib, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, site-compat)
(This is something we have no short-term plan for doing, so this is bookkeeping.)
Like Safari, we decided against ever implementing navigator.getUserMedia
, the spec's legacy api—We want to help drive convergence around the modern promise-based navigator.mediaDevices.getUserMedia
instead.
Instead, our legacy answer is keep navigator.mozGetUserMedia
around until usage drops (it may never drop, perhaps due to trackers which tend to prefer conservative patterns for broadest reach).
Updated numbers (still beta due to bug 1517018): 9.5% (74851/788853) of gum calls are callback-based, down from 21% in bug 1279936 comment 5 from bug 1528031.
Chromestatus says 9.3% of gUM calls are callback-based still (0.005277/0.056918), so that seems about right.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
•
|
||
Progress on this bug would rely on getting the usage number down. Improved telemetry to discount failing getUserMedia
calls may help weed out trackers using the API for fingerprinting.
Updated•2 years ago
|
Comment 2•1 year ago
|
||
This has Deprecated="NavigatorGetUserMedia"
in Navigator.webidl
What do the use counters look like now?
Comment 4•1 month ago
|
||
This should be documented in the related browser compat data.
Sebastian
Reporter | ||
Comment 5•7 days ago
•
|
||
(In reply to comment #0)
Updated numbers:
navigator.mozGetUserMedia
: 0.00259% vs.navigator.mediaDevices.getUserMedia
: 0.0642%
Chromestatus says 9.3% of gUM calls are callback-based still (0.005277/0.056918), so that seems about right.
Chromestatus now says only 3.2% of gUM calls are callback-based (0.005935/0.184198).
But we see this is because promise-based gUM usage has trippled over the last 4 years whereas callback usage has stayed the same.
Description
•