- From: <bugzilla@jessica.w3.org>
- Date: Thu, 10 Apr 2014 09:28:50 +0000
- To: public-media-capture@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25275 --- Comment #2 from Kiran <kiran.guduru@samsung.com> --- AFAIK It should be -1. It varies when we consider different scenarios. The following is my thinking regarding this. case 1: If no tracks are present it should be -1. (current spec is not explicitly specifying about this). If we set -1 as default value, this case will be handled by default. case 2: Current spec is specifying that, it should be set to first available enabled / un-muted track. It is not explicitly specifying anything about selecting the first track after it is enabled or un-muted. (means it says to continue with the already selected track) case 3: If more than one track is present, for example 2, and the second track is selected at the time of initialization, then after some time if the selected track is removed and first track got ended because of some reason. In this case, spec is not explicitly specifying which track need to be selected. case 4: If the first track is muted (and only one is present) and a new track is added after some time (which is enabled and un-muted), spec should explicitly specify it to select the new track. case 5: As Adam specified if the track is disabled or muted, then enabled after some time then it would played (This is a positive scenario). Instead of defining different values in each case, it is good to set -1 by default (if no track present or track is disabled / muted) and change its value to required track number in the list, in case like when a track is added or enabled or un-muted. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Received on Thursday, 10 April 2014 09:28:51 UTC