- From: <bugzilla@jessica.w3.org>
- Date: Thu, 03 Nov 2011 17:11:10 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14260 --- Comment #26 from Philip Jägenstedt <philipj@opera.com> 2011-11-03 17:11:08 UTC --- As Simon pointed out in IRC, it's a bit odd that <track> inserted by script behaves completely differently from <track> inserted by the parser. Perhaps another way is to define that </video> invokes the resource selection algorithm and to instead consider all child <track> elements the last time the resource selection algorithm was invoked to block the transition to HAVE_CURRENT_DATA? To avoid taking an actual snapshot of the list of <track> elements, I'd probably implement it as a "blocking" flag that is set to true for child <track> elements when the resource selection algorithm runs. P.S. I suggest blocking HAVE_CURRENT_DATA rather than HAVE_FUTURE_DATA because a cue might begin at 0. -- 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 Thursday, 3 November 2011 17:11:19 UTC