Open Bug 1609254 Opened 4 years ago Updated 7 days ago

Deprecate navigator.mozGetUserMedia()

Categories

(Core :: WebRTC: Audio/Video, task, P5)

task

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.

  • navigator.mozGetUserMedia: 0.002% vs.
  • navigator.mediaDevices.getUserMedia: 0.026%

Chromestatus says 9.3% of gUM calls are callback-based still (0.005277/0.056918), so that seems about right.

No longer blocks: 1531812
Severity: normal → minor
No longer depends on: 1279936
Priority: P3 → P5
See Also: → 1279936

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.

See Also: → 1531812
Severity: minor → S4

This has Deprecated="NavigatorGetUserMedia" in Navigator.webidl

What do the use counters look like now?

Flags: needinfo?(jib)
Blocks: unprefix
Depends on: 1155923
Depends on: 1528078
Duplicate of this bug: 1210558

This should be documented in the related browser compat data.

Sebastian

Keywords: dev-doc-needed

(In reply to comment #0)

  • navigator.mozGetUserMedia: 0.002% vs.
  • navigator.mediaDevices.getUserMedia: 0.026%

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.

Flags: needinfo?(jib)
You need to log in before you can comment on or make changes to this bug.