[Bug 25652] New: Media Capture Spec should explicitly specify about MediaStream active / inactive state change events to give more clarity.

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

            Bug ID: 25652
           Summary: Media Capture Spec should explicitly specify about
                    MediaStream active / inactive state change events to
                    give more clarity.
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Capture and Streams
          Assignee: public-media-capture@w3.org
          Reporter: kiran.guduru@samsung.com
                CC: public-media-capture@w3.org

Media Capture and Streams spec is specifying active / inactive events.
But missing to give clarity about when they should be fired and when they
should not be fired, if any.

MediaStream state may change in many aspects other than MediaStream Constructor
algorithm, like
if the following functions invoked 
MediaStream.addTrack()
MediaStream.clone()
MediaStream.removeTreack()
MediaStramTrack.stop()
MediaStreamTrack.enabled()

or if the addTrack/removeTrack events ocrrucred because of internal
peerConnection changes
or if all the tracks get muted because of external entity.

Spec should specify that the corresponding active / inactive event should be
fired.
Adding the following line after
"Otherwise the stream is active. A MediaStream can start its life as inactive
if it is constructed without any tracks"
"UA should fire active and inactive events whenever the stream changes its
state from inactive to active and active to inactive respectively"
may be sufficient.

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

Received on Saturday, 10 May 2014 13:49:25 UTC