[Bug 24928] the spec defines the addtrack event as part of the MediaStream interface, but never calls out when the event should be fired.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24928

Adam Bergkvist <adam.bergkvist@ericsson.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adam.bergkvist@ericsson.com

--- Comment #1 from Adam Bergkvist <adam.bergkvist@ericsson.com> ---
Hi and thanks for providing feedback on the spec.

The question whether the "addtrack" event should be fired as a result of
MediaStreamTrack.addTrack() has been brought up a few times before.

The event is intended to asynchronously notify the script that the platform has
updated the stream's track set. The new track is added to the track set as the
event is dispatched. Direct manipulation with addTrack() doesn't need the event
since the new track is added synchronously; i.e. you can, e.g., read out the
new track set length on the next line of code. Having the event could on the
other hand complicate things since by the time the event is dispatched, the
track could have been removed already.

The question is if the definition of the event should be in this spec or if it
should be defined where it's actually used.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Received on Wednesday, 5 March 2014 13:52:30 UTC