Open Bug 1179084 Opened 9 years ago Updated 29 days ago

Implement MediaStreamTrack::getCapabilities() and MediaTrackCapabilities

Categories

(Core :: WebRTC: Audio/Video, enhancement, P3)

Product:
Core
Component:
WebRTC: Audio/Video
Type:
enhancement

Tracking

()

Project Flags:
Webcompat Priority P2
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: mathieu.hofman.dev+mozilla, Assigned: jib)

References

(Blocks 4 open bugs)

Details

(Keywords: dev-doc-needed, parity-chrome, parity-safari) 

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36

Steps to reproduce:

Call MediaStreamTrack::getCapabilities()


Actual results:

Method doesn't exist


Expected results:

Method returns a MediaTrackCapabilities object.
Request to implement MediaStreamCapabilities (http://w3c.github.io/mediacapture-main/getusermedia.html#media-track-capabilities)
Flags: needinfo?(jib)
Assignee: nobody → jib
Flags: needinfo?(jib)
Status: UNCONFIRMED → NEW
backlog: --- → webrtc/webaudio+
Rank: 25
Component: Audio/Video → WebRTC: Audio/Video
Ever confirmed: true
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Blocks: 1437002

Any chance this feature will come in near future?

See Also: → 1573356
Type: defect → enhancement

Reminder to check the privacy.resistFingerprinting pref as well as bug 1528042 when implementing this feature.

See Also: → 1528042

Any chance this feature will come in near future?

It's been 2 years. Any news?

This is currently breaking Facebook Messenger Calls, see the linked WebCompat bug. I've already reached out to them to see if they can fix it, but I'm setting a webcompat-priority here for now so that this is on our radar.

Webcompat Priority: --- → P1
See Also: → https://github.com/webcompat/web-bugs/issues/109006

... aaaand they fixed it. :)

Webcompat Priority: P1 → ---
Severity: normal → S3
Webcompat Priority: --- → ?
Webcompat Priority: ? → P2
Blocks: 1886719
You need to log in before you can comment on or make changes to this bug.