W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14260] <track> "text tracks ready" and HTMLMediaElement.readyState

From: <bugzilla@jessica.w3.org>
Date: Wed, 26 Oct 2011 22:29:31 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RJByV-0005FW-6X@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14260

--- Comment #22 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-26 22:29:29 UTC ---
Hmm... I started speccing this, and I'm not sure I'm 100% comfortable with some
of the implications here.

What exactly are we blocking on? Consider what happens if a text track is
removed from a media element, is disabled, or is enabled, between the <track>
element being parsed and the </video> tag being parsed. Which ones should
block? What about tracks that are dynamically added? Consider a setTimeout()
script racing the parser to add or remove something from the list, or an
onerror handler on a <track> that updates the src="", racing with the parser:

   <video>
     <track ... onerror="update track src">
     ...
   </video>

Exactly which tracks should we wait for?

-- 
Configure bugmail: http://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 Wednesday, 26 October 2011 22:29:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:06 UTC