Thanks so much for clarifying the whole caller/receiver semantics around data channels. I've read dozens of different sites and demos around webrtc and never picked up on that detail. Need Moar Better Docs! :)
So, I implemented the change, and now FF works! Hooray. But, it broke Chrome (Canary). In fact, in a stunning turn of irony, it broke Chrome in the same symptomatic way that FF was previously broken. That is, both sides appear to have the Data Channel (the caller onopen fires and the receiver ondatachannel fires). BUT, sending data across the channel, it never gets to the other side now, whereas before data flowed freely in Chrome when there were two channels. I know this isn't a Chrome support forum, so now I guess I get to shift my question over to their "support". But it's still just a major bummer for us devs (even knowing how "bleeding edge" this stuff is) that it's so hard to get code that works in both browsers. I know data-channels are "new" but they HAVE been around for a year now and it's still just so painful. :) Thanks again! --Kyle _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
