Re: [webrtc-pc] Does direction matter for rejected m= sections? (#1812) from Jan-Ivar Bruaroey via GitHub on 2019-03-06 (public-webrtc-logs@w3.org from March 2019)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Wed, 06 Mar 2019 21:31:20 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-470284962-1551907878-sysbot+gh@w3.org>

[Turns out](https://jsfiddle.net/jib1/zroe80px/) I missed that Firefox offers `a=inactive` after `transceiver.stop()`—apparently to avoid interop headaches—which somewhat wrecks my [earlier argument](https://github.com/w3c/webrtc-pc/pull/1845#issuecomment-385675103) for closing this. Re-opening.

I suggest we enshrine that behavior in the spec, and open a bug on Firefox to add the missing events (Firefox still doesn't fire the respective `mute` and `removetrack` events on the other end from it).

Chrome doesn't implement transceiver.stop() yet AFAIK. @henbos Does that sound good?

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1812#issuecomment-470284962 using your GitHub account

Received on Wednesday, 6 March 2019 21:31:23 UTC