15729 2012-01-26 15:27:15 +0000 The editors draft doesn't specify what should happen if a null stream is added to a PeerConnection 2012-01-27 09:34:24 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified PC All RESOLVED INVALID P2 normal --- 1 tommyw public-webrtc adam.bergkvist harald public-webrtc oldest_to_newest 63151 0 tommyw 2012-01-26 15:27:15 +0000 Since the stream can be undefined/null the specification needs to say, at a minimum: Step 0: if stream is undefined or null return. 63157 1 adam.bergkvist 2012-01-26 16:50:43 +0000 The addStream() stream argument isn't nullable so we don't have to deal with null in the algorithm. If I'm not mistaking it will cause a TypeError. 63158 2 tommyw 2012-01-26 17:53:03 +0000 The editors draft from Jan 12th clearly marks the stream argument to addStream as both nullable and optional. 63176 3 adam.bergkvist 2012-01-27 09:30:55 +0000 Are you referring to the parameter table for addStream()? A red cross means "no", while a green check-thingy means "yes". Is this the best possible style? Perhaps not, since a table with only red crosses is easily misinterpreted. 63177 4 tommyw 2012-01-27 09:34:24 +0000 Doh, an x means no... Sorry! Especially for colour-blind people it is much better if one only uses check-thingies for yes and empty cells for no.