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

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Mar 2011 07:16:45 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pxwab-00022e-7W@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #12 from Philip Jägenstedt <philipj@opera.com> 2011-03-11 07:16:44 UTC ---
(In reply to comment #11)
> (In reply to comment #10)
> > The initial scope of this bug was to make the transitions of readyState and
> > networkState happen in the same task that fires the related event. 
> > 
> 
> Comment #0 says "*all*" properties should be frozen while events are pending:

Oops, I was reading the title of the bug when I wrote that. Still, I don't
think it's a given that we must freeze everything, so let's discuss the actual
pros and cons.

Starting at readyState and networkState, do you at all agree that what we have
now is problematic? Do you think see a problem with making "video state
transitions happen in the same task as firing events"?

-- 
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 Friday, 11 March 2011 07:16:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 11 March 2011 07:16:53 GMT