1512517 - Update WebRTC stat deprecation warnings

Status: RESOLVED FIXED

(Core :: WebRTC, enhancement, P1)

Description

[Nico Grunbaum [:ng, @chew:mozilla.org]]

The WebRTC stats deprecation warnings that were originally scheduled for 65.

Comment 1

[Nico Grunbaum [:ng, @chew:mozilla.org]]

Attachment: Bug 1512517 - update WebRTC stat deprecation messages

Update WebRTC stat deprecation messages which were originally targeting 65, which are now targeting 66.

Comment 2

[Nico Grunbaum [:ng, @chew:mozilla.org]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=70135e9047d695b72afa108dfc63c8c2845f90e9

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6725a7f43bae
update WebRTC stat deprecation messages r=jib

Comment 4

[Razvan Maries]

https://hg.mozilla.org/mozilla-central/rev/6725a7f43bae

Comment 5

[Kohei Yoshino [:kohei]]

Updated site compatibility notes:

https://www.fxsitecompat.com/en-CA/docs/2016/rtcstatsreport-has-become-map-like-object/
https://www.fxsitecompat.com/en-CA/docs/2017/callback-based-rtcpeerconnection-getstats-has-been-deprecated/
https://www.fxsitecompat.com/en-CA/docs/2018/rtcrtpstreamstats-isremote-has-been-deprecated/

Comment 6

[Chris Mills [:cmills]]

Note to MDN writers:

These are deprecations rather than removals, so I'm not sure if it is worth reporting these in the Fx65 rel notes.

When you do come to document these, there'll be some compat data and descriptions to update on the actual ref pages.

Comment 7

[Eric Shepherd [:sheppy]]

Notes to self:

Our docs do not even mention the past existence of a callback-based getStats(). I need to decide whether to worry about this at all at this point. I will probably not update the doc content, but just add a note to BCD about the deprecation of the callback form and the addition of the promise form if that's not there yet.

Comment 8

[Eric Shepherd [:sheppy]]

There's really nothing to do here documentation (or BCD)-wise until these are actually removed. Just outputting warnings doesn't require any changes on our end to speak of. Please make sure the bug to actually remove these features has the dev-doc-needed keyword.