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: Thu, 10 Mar 2011 22:55:25 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PxolR-0000GZ-D4@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #11 from Eric Carlson <eric.carlson@apple.com> 2011-03-10 22:55:23 UTC ---
(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:

    The video spec should be overhauled so that state transitions and events
happen
    at the same time, so that things are predictable, testable and easier to
author
    against.

    If we do this, we also need to freeze *all* state to keep things in sync.
If
    other properties are still allowed to change while the script is running,
    weirdness ensues:

[SNIP]

    In short, if not all properties are frozen, they can become internally
    inconsistent as seen from scripts. Freezing one property would require
freezing
    them all instantaneously, or they could stil become inconsistent. Freezing
all
    of them means always calculating the buffered array even though it may not
be
    used, which is a bit wasteful.

-- 
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, 10 March 2011 22:55:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 March 2011 22:55:35 GMT