Re: Specify the negotiationneeded event

> I wanted to clarify. As far as I know Chrome currently fires two
> negotiationneeded events when removeTrack is immediately followed by
> addTrack. Is this going to change based on this specification and only one
> negotiationneeded event will be fired?

It should fire only one, and in a second iteration/implementation
detail/left for a future specification, being so smart to detect the
inverse operation (addTrack/removeTrack) leading to the same previous
state and don't dispatch it at all since nothing changed.


-- 
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
Unix."
– Linus Tordvals, creador del sistema operativo Linux