Re: [webrtc-pc] Does direction matter for rejected m= sections? (#1812)

[Turns out]( I missed that Firefox offers `a=inactive` after `transceiver.stop()`—apparently to avoid interop headaches—which somewhat wrecks my [earlier argument]( 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 using your GitHub account

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