[WebAPI] WebRTC Deprecate non-standard frameRateMean and frameRateStdDev stats

[Rumyra]

Acceptance Criteria

• The listed features are documented sufficiently on MDN
• BCD is updated - NA
• Interactive example and data repos are updated if appropriate - NA
• The content has been reviewed as needed

For folks helping with Firefox related documentation

• Set bugs to dev-doc-complete
• Add entry to Firefox release notes if feature is enabled in release
  or
• Add entry to Firefox experimental features page if feature is not yet enabled in release

Features to document

WebRTC - Deprecate non-standard frameRateMean and frameRateStdDev stats - check through docs & BCD to reflect.

Related Gecko bugs

https://bugzilla.mozilla.org/show_bug.cgi?id=1367562

[hamishwillee]

The webidl shows these 5 properties removed: droppedFrames, bitrateMean, bitrateStdDev, framerateMean, framerateStdDev.

I did a search on these and none are in mdn or bcd. I also looked in the associated classes like: RTCOutboundRtpStreamStats, RTCOutboundRtpStreamStats and the sub classes in the chain. This all needs to be looked at again?

I found https://groups.google.com/g/discuss-webrtc/c/pkAtJEF_unM which discusses the changes. This covers this bug, but also reports removal of bytesReceived on "remote-inbound-rtp" stats. This might mean we need to remove RTCInboundRtpStreamStats.bytesReceived and/or RTCIceCandidatePairStats.bytesReceived. Might not - checking.

@Rumyra Is it worth adding a release note for this - given there is no evidence of this stuff every having being supported?

• Release note - FF96 Relnote: WebRTC Stats removed #11019
• dev-doc-complete

[Rumyra]

Yes I think it's worth a rel note just for brevity - but it looks as tho nothing else is needed 👍

[hamishwillee]

Thanks. I've done the release note but I'll hold off on dev-doc-complete and moving this to closed until Friday to give that team time to confirm nothing else needs to be done

[hamishwillee]

@Rumyra So they got back to me in https://bugzilla.mozilla.org/show_bug.cgi?id=1367562#c7. The relevant bit is:

As part of bug 1654112 I most certainly think we should add a relnote for developers on this huge update. Those "sampling of improvements" bugs might not need any mention in relnotes (or docs -- they're bug fixes rather than features).

In other words, this bug in itself is nothing much but is part of a much bigger story in https://bugzilla.mozilla.org/show_bug.cgi?id=1654112

But I can't tell from that bug report what is relevant, or whether this is important to the MDN docs release process. My guess is that it is irrelevant to the MDN docs, but very relevant to the product.

Do you fancy chasing the big picture on this? If it were me I'd ask against that "bigger story bug" for the engineering team to suggest a release note - because we can't access the scope of change.

[Rumyra]

But I can't tell from that bug report what is relevant, or whether this is important to the MDN docs release process. My guess is that it is irrelevant to the MDN docs, but very relevant to the product.

In a word yes...

By the looks of the main bug is part of a big update to the webRTC backend rather than any changes to the implementation of the spec (apart from above) - in which case this is the FF engineers domain for release notes under Firefox itself and not MDN.

I'll keep my eye on the original bug above as someone replied yesterday, but I don't think there's anymore to do from our end on this 👍

[hamishwillee]

Great. Moving to done and closing then (also set dev-doc-complete)