-
Notifications
You must be signed in to change notification settings - Fork 34
More WebIDL Issues #97
Description
From: Jason Ausborn jason.ausborn@gmail.com
Date: Sun, 15 Jun 2014 11:12:51 -0500
To: "public-ortc@w3.org" public-ortc@w3.org
URL: http://lists.w3.org/Archives/Public/public-ortc/2014Jun/0038.html
Possible Issue Location : 2.3 Interface Definition (interface
RTCDtlsTransport)
Possible Issue : Inside the interface we have a sequence, but
ArrayBuffer is not a WebIDL type, and we don't have it defined anywhere
else.
Possible Issue Location :
4.3 Infterface Definition (interface RTCIceTransportController)
Possible Issue : int is not a valid WebIDL type for addTransport (..., int
index) parameter.
Possible Issue Location 1 :
9.4 dictionary RTCRtcCodecCapability
Possible Issue Location 2:
9.7 dictionary RTCRtcCodecParameters
Possible Issue : Inside the dictionary we have a Dictionary type for
parameters, I don't think it is valid syntax to have a dictionary
type inside a dictionary.
Possible Issue Location : 11.3 Interface Definition (interface
RTCDataChannel)
Possible Issue 1: We have a Promise type used in the interface, but Promise
is not a WebIDL type, and we don't have a Promise type defined anywhere
else.
Possible Issue 2: We have an ArrayBuffer type used for RTCDataChannel.data,
but ArrayBuffer is not a WebIDL type, and we don't have ArrayBuffer defined
anywhere else.
Possible Issue Location : 13 Statistics API & 13.5 RTCStats Dictionary
Possible Issue : In section 13 we have a RTCStats interface, but we also
have a dictionary in 13.5 named RTCStats. Since they have the same name,
there is a clash. We might want to change the name of one of them.
Possible Issue Location 1:
6.3 Interface Definition (interface RTCRtpSender)
Possible Issue Location 2:
7.3 Interface Definition (interface RTCRtpReceiver)
Possible Issue : We don't have the MediaStreamTrack type defined anywhere.
HTH