[Web API] Support RTCInboundRtpStreamStats.trackIdentifier

[Rumyra]

Acceptance Criteria

• The listed features are documented sufficiently on MDN
• BCD is updated
• Interactive example and data repos are updated if appropriate
• 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
• Add entry to Firefox experimental features page if feature is not yet enabled in release

Related Gecko bugs

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

Other

• Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
• Check if glossary updates are required for the feature you're documenting - whether an existing term needs to be updated or a new term should be added.
• Check if BCD update means that content pages need to have experimental markup removed or deprecated markup added (front matter tags and macros).

[hamishwillee]

Status

• BCD - Not done - deferred to WebRTC stats - update to spec and remove dictionaries mdn#384
  • Note, started work in RTCStatsReport - add stats-type features and stats browser-compat-data#18910 and that moved into the above project
• Docs -
  • Basic docs for just the property FF111 supports RTCInboundRtpStreamStats.trackIdentifier #24423
• Release note - FF111 supports RTCInboundRtpStreamStats.trackIdentifier #24423
• dev-doc-complete

Note, the work already done is "enough for release".

Remaining work has been pushed to own-project: mdn/mdn#384

[hamishwillee]

@Rumyra I have done the minimal work on this - there is a release note and that links to the now-supported feature RTCInboundRtpStreamStats.trackidentifier.

There is no BCD but otherwise that is kind of enough "for release".

However this has taken forever because I have tried to do the job properly and remove the RTCInboundRtpStreamStats dictionary. What actually happens is that RTCPeerConnection.getStats() returns an RTCStatsReport, and iterable object that you can loop through to get a number of different sets of named stats. The RTCInboundRtpStreamStats are just a part of one of these sets called inbound_rtp.

I have started the BCD work in mdn/browser-compat-data#18910 but we're balked by the tests not working. In discussion with Vinyl on that, but there are 100s of items in there.

Next step would be to update RTCPeerConnection.getStats() with all the possible values it can return - thats the 100s of values in that BCD above. We'd start from the spec and BCD, pull in the existing dictionaries, then hide anything for which there is no implementation yet.

Upshot, will not do for this release - simply not possible. I was thinking we might create a separate project for RTC stats I can do as a background and close this as done?

[Rumyra]

Let's create a separate project @hamishwillee - do you want to outline it here https://github.com/mdn/mdn/issues/new?assignees=&labels=proposal%2Cneeds+triage&template=content-or-feature-suggestion.yml&title=Enter+your+proposal+here and we'll run it aside from the ff project?

[hamishwillee]

@Rumyra Done - project is here: mdn/mdn#384

I've updated this issue, which is now "done".