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

[Bug 12267] <video> Make video state transitions happen in the same task as firing events

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Aug 2011 09:59:12 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QoBkm-0000Mu-3v@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #49 from Philip Jägenstedt <philipj@opera.com> 2011-08-02 09:59:11 UTC ---
(In reply to comment #48)
> (In reply to comment #47)
> > If the readyState change is delayed, the video can't start playing (unless we
> > are decoupling the video logic from the readyState, which I thought you said in
> > comment 40 we should not do).
> 
> I didn't mean to imply that. In Firefox the playback engine can advance through
> its internal states freely while the script-visible readyState is only updated
> between tasks.

This sounds similar to Opera, where the state of the media pipeline is most
definitely not coupled synchronously to readyState. Decoding happens on
separate thread while readyState is updated asynchronously on the main thread.

-- 
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 Tuesday, 2 August 2011 09:59:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:15 UTC