- From: <bugzilla@jessica.w3.org>
- Date: Sat, 12 Nov 2011 21:45:42 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14260 --- Comment #30 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-11-12 21:45:32 UTC --- (In reply to comment #29) > So: > > - if the media element is still on a stack of open elements, then abort the > resource selection algorithm at the top. > - when a media element is popped off a stack of open elements, run the resource > selection algorithm. > - when the resource selection algorithm is started, flag any <track> elements > in the media element as being load-blocking text tracks. > - when a text track loads or fails to load, clear its load-blockingness. > - prevent transition to HAVE_FUTURE_DATA when there are any tracks in the media > element's list of text tracks that are load-blocking. > > Sound right? Sounds good to me. Can we additionally have a timeout on the load-blockingness of tracks? Maybe "fails to load" already has a timeout, then that's fine. I just want to make sure the video doesn't get starved because a connection waits indefinitely on a text track. -- 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 Saturday, 12 November 2011 21:45:45 UTC