mdn / mdn/browser-compat-data

api.RTCStatsReport.type_inbound-rtp.nackCount - reported by at least Safari for iOS 17.1.2

Open
#22,293 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:api
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Data quality

What information was incorrect, unhelpful, or incomplete?

nackCount is reported by at least Safari for iOS 17.1.2 and probably other browsers at older versions.

What browsers does this problem apply to, if applicable?

Safari, Chrome, Firefox

What did you expect to see?

If support status is unknown or hasn't been captured, I would expect the table to reflect that instead of definitively saying the feature is unsupported.

Did you test this? If so, how?

Yes, I reviewed the output of the stats API reported by a Safari for iOS 17.1.2 client and a Chrome Mobile WebView 121 client and @hamishwillee reviewed the output of Chrome 121 and Firefox 123 user agents.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/RTCInboundRtpStreamStats/nackCount

MDN metadata
MDN page report details
  • Query: api.RTCStatsReport.type_inbound-rtp.nackCount
  • Report started: 2024-02-26T16:08:40.271Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MDN RTCInboundRtpStreamStats/nackCount page and the BCD entry identified by the query api.RTCStatsReport.type_inbound-rtp.nackCount. Compare the recorded Safari, Chrome, and Firefox support data with the reported API output; done means the compatibility table no longer definitively marks the feature unsupported when support is unknown or present.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.