This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15729 - The editors draft doesn't specify what should happen if a null stream is added to a PeerConnection
Summary: The editors draft doesn't specify what should happen if a null stream is adde...
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
Depends on:
Reported: 2012-01-26 15:27 UTC by tommyw
Modified: 2012-01-27 09:34 UTC (History)
3 users (show)

See Also:


Description tommyw 2012-01-26 15:27:15 UTC
Since the stream can be undefined/null the specification needs to say, at a minimum:
Step 0: if stream is undefined or null return.
Comment 1 Adam Bergkvist 2012-01-26 16:50:43 UTC
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.
Comment 2 tommyw 2012-01-26 17:53:03 UTC
The editors draft from Jan 12th clearly marks the stream argument to addStream as both nullable and optional.
Comment 3 Adam Bergkvist 2012-01-27 09:30:55 UTC
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.
Comment 4 tommyw 2012-01-27 09:34:24 UTC
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.