Some RTC pages reference missing BCD identifiers

Open
#46,383 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #46389 by @ump45nose — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
57/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript

Research direction

Start with the eight linked Markdown pages under files/en-us/web/api/rtcicecandidatepairstats, rtcicecandidatestats, and rtcicetransport, then check the referenced browser compatibility data history in PR 18910. Determine whether each page should be removed or its compatibility reference updated; done when all eight pages no longer produce missing BCD identifier warnings.

Written by the indexing model from the issue text.

Description

Content:WebAPI needs info
MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/RTCIceCandidatePairStats/availableIncomingBitrate etc

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

There are 8 pages that point to BCD data removed 3 years ago in https://github.com/mdn/browser-compat-data/pull/18910, with a warning like this:

No compatibility data found for api.RTCStatsReport.type_candidate-pair.availableIncomingBitrate.

What did you expect to see?

Probably the pages shouldn't exist.

Do you have any supporting links, references, or citations?

8 issues — live view

Filters:

  • category: templ-bcd-missing
  • locale: en-US
  • file: web/api/rtc
File Slug Message
content/files/en-us/web/api/rtcicecandidatepairstats/availableincomingbitrate/index.md:33:1 Web/API/RTCIceCandidatePairStats/availableIncomingBitrate Unknown browser-compat entry: api.RTCStatsReport.type_candidate-pair.availableIncomingBitrate
content/files/en-us/web/api/rtcicecandidatepairstats/readable/index.md:35:1 Web/API/RTCIceCandidatePairStats/readable Unknown browser-compat entry: api.RTCStatsReport.type_candidate-pair.readable
content/files/en-us/web/api/rtcicecandidatepairstats/selected/index.md:55:1 Web/API/RTCIceCandidatePairStats/selected Unknown browser-compat entry: api.RTCStatsReport.type_candidate-pair.selected
content/files/en-us/web/api/rtcicecandidatepairstats/writable/index.md:39:1 Web/API/RTCIceCandidatePairStats/writable Unknown browser-compat entry: api.RTCStatsReport.type_candidate-pair.writable
content/files/en-us/web/api/rtcicecandidatestats/deleted/index.md:82:1 Web/API/RTCIceCandidateStats/deleted Unknown browser-compat entry: api.RTCStatsReport.type_local-candidate.deleted
content/files/en-us/web/api/rtcicecandidatestats/relayprotocol/index.md:41:1 Web/API/RTCIceCandidateStats/relayProtocol Unknown browser-compat entry: api.RTCStatsReport.type_local-candidate.relayProtocol
content/files/en-us/web/api/rtcicecandidatestats/url/index.md:32:1 Web/API/RTCIceCandidateStats/url Unknown browser-compat entry: api.RTCStatsReport.type_local-candidate.url
content/files/en-us/web/api/rtcicetransport/component/index.md:28:1 Web/API/RTCIceTransport/component Unknown browser-compat entry: api.RTCIceTransport.component
Do you have anything more you want to share?

No response

Dominant language
Markdown
Stars
11.1k
Forks
23.3k
Avg merge
2d 12h
Merged PRs (30d)
187

Getting set up

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.

More from mdn/content

All issues in mdn/content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.