-
Notifications
You must be signed in to change notification settings - Fork 42
Closed
Description
Throughout the specification, there appear to be issues with methods that can return null or attributes that can be null. For example:
- If getLocalCandidates() is called before gather() had been called, there are no local candidates. So should getLocalCandidates() return an empty list?
- What does getRemoteCandidates() return if there aren't any remote candidates yet? An empty list?
- In getRemoteCertificates(), what if the remote certificates aren't available yet? Can getRemoteCandidates return an empty list?
- Why is RTCDtlsTransportState nullable in RTCDtlsTransportStateChangedEventInit?
dictionary RTCDtlsTransportStateChangedEventInit : EventInit {
RTCDtlsTransportState? state;
}; - In the RtpSender, what if an rtcpTransport isn't provided? Shouldn't the rtcpTransport attribute be nullable?
partial interface RTCRtpSender : RTCStatsProvider {
readonly attribute RTCDtlsTransport? rtcpTransport;
};
- In the RtpReceiver, what if an rtcpTransport isn't provided? Shouldn't the rtcpTransport attribute be nullable?
partial interface RTCRtpReceiver : RTCStatsProvider {
readonly attribute RTCDtlsTransport? rtcpTransport;
};
- The RTCIceTransportController
What if there aren't any ICE transports added yet? Does getTransports() return an empty list?