Some RTC pages reference missing BCD identifiers
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
- Domain
- documentation, web-dev
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
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?
Filters:
- category:
templ-bcd-missing - locale:
en-US - file:
web/api/rtc
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mdn/content
-
Add the message_serialization manifest key page and update the data cloning algorithm sectionPossibly taken A pull request linked to this issue is open or already merged. OpenContent:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
CSS Custom Highlight API: mention StaticRange for highlights that outlive DOM changesPossibly taken @abdul-karim-mia claimed this 4 days ago. OpenContent:WebAPI help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Content:Meta needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
can `name` of objects in `webRequest.HttpHeaders` repeat?Possibly taken @Ashish-CodeJourney claimed this 2 days ago. OpenContent:WebExt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mdn/content#46472 · 1 comment ·
Maintainers usually reply within 1 day
-
`filter` creating a containing block unmentionedPossibly taken @Ganeshguru5 claimed this 4 days ago. OpenContent:CSS
Difficulty 1/5 Under an hour Newbie friendliness 75/100
mdn/content#46414 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
molgenis/molgenis-emx2#7059 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-format
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Niko1221/Strata#6251 · 1 comment ·
Maintainers usually reply within 5 days
-
area: plugins documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
CatVinci-Studio/Textus#727 ·
Maintainers usually reply within 1 day