- From: <bugzilla@jessica.w3.org>
- Date: Mon, 14 May 2012 20:55:28 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17002 --- Comment #2 from Aaron Colwell <acolwell@chromium.org> 2012-05-14 20:55:28 UTC --- (In reply to comment #1) > (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? I accidentally forgot to mention TextTrack, but now that I'm looking at the HTML5 spec, it appears that TextTrack doesn't have an id attribute like AudioTrack and VideoTrack do. It isn't clear to me why this is. Perhaps an oversight? I agree TextTrack should be included, but we should resolve the lack of id attribute before updating the Summary for this bug. > > 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? I wasn't aware that you could fetch AudioTrack or VideoTrack objects by using getElementById(). Please point me to the relevant spec text. You are right though that SourceIDs are only unique with within a specific HTMLMediaElement. I was under the assumption that AudioTrack.id and VideoTrack.id only needed to be unique within the HTMLMediaElement. Could you point me to text in the spec that indicates it must be globally unique within the document. I can't seem to find it. -- 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 Monday, 14 May 2012 20:55:32 UTC