mdn / mdn/browser-compat-data

api.RTCRtpSender.setParameters et al. - missing scalabilityMode param option

Open
#25,720 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

There are some extensions for SVC in WebRTC in https://w3c.github.io/webrtc-svc/ - these were implemented in Chrome in 111 as per
https://chromestatus.com/feature/5769626174619648

The change appears to be an addition to the dictionary RTCRtpEncodingParameters of scalabilityMode

partial dictionary RTCRtpEncodingParameters {
             DOMString scalabilityMode;
};;

RTCRtpEncodingParameters is used in several places including

Param needs to be updated in those

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

Subfeatures.

Did you test this? If so, how?

By inspection, but you can also test using https://wpt.live/webrtc-svc/RTCRtpParameters-scalability.html

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

https://github.com/mdn/content/pull/37722 (we report the stats, just don't allow them to be set in this way)

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response

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 by reviewing the RTCRtpSender.setParameters and RTCPeerConnection.addTransceiver compatibility entries, using the WebRTC SVC specification and the linked wpt.live test. Done means scalabilityMode is represented as a subfeature wherever RTCRtpEncodingParameters is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.