Open Bug 1806181 Opened 1 year ago Updated 1 year ago

We should be throwing InvalidAccessError for semantically invalid SDP

Categories

(Core :: WebRTC: Signaling, defect, P3)

defect

Tracking

()

People

(Reporter: bwc, Unassigned)

References

Details

Right now we're throwing OperationError for both syntax and semantics errors in SDP. This is not quite right. webrtc-pc says we should throw:

  • RTCError with ''sdp-syntax-error" when the SDP is syntactically malformed
  • InvalidAccessError for semantics errors (this is phrased as "If the content of description is invalid", which is pretty vague)
  • OperationError for other errors
Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.