- From: <bugzilla@jessica.w3.org>
- Date: Fri, 11 May 2012 19:46:43 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17002
Bob Lund <b.lund@cablelabs.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |b.lund@cablelabs.com
--- Comment #1 from Bob Lund <b.lund@cablelabs.com> 2012-05-11 19:46:42 UTC ---
(In reply to comment #0)
> The current spec does not provide a way for a web application to determine
> which SourceID an AudioTrack or VideoTrack is associated with. This makes it
> difficult for the application to determine what the current Active ID set is.
>
> A simple solution would be to place the SourceID in the AudioTrack.id &
> VideoTrack.id fields
What about TextTrack?
Does using the SourceId guarantee uniqueness so it can be used by
getElementById()? Aren't SourceIDs only unique with respect to an instance of
HTMLMediaElement?
> along with some sort of delimiter and the format native
> trackID.
Having the format native trackID in the VideoTrack, AudioTrack and TextTrack
for in-band tracks would also be useful so that metadata about the media
resource could be associated with Video, Audio and Text tracks.
>
> Some id possibilities for SourceID 'source1' & format native TrackID 2:
> source1:2
> source1-2
> source1,2
>
> The choice of delimiter would require escaping rules or restrictions on what
> characters would be allowed in sourceID strings. Currently no restrictions
> exist in the text.
>
> Adding the sourceID to the id field also helps keep the id for each track
> unique so that Audio|VideoTrack.getTrackById() works as expected.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 11 May 2012 19:46:46 UTC