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: Tue, 08 Mar 2011 19:20:34 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Px2SQ-0005xY-IO@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

David Singer <singer@apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |singer@apple.com

--- Comment #2 from David Singer <singer@apple.com> 2011-03-08 19:20:33 UTC ---
There seem to be two problems here:
(a) a script handling an event may be reacting to an 'old' state and (b) when
testing, it's hard to verify behavior if it's time-dependent and not
predictable.

We can't freeze the video while we process events; I assume that's not what is
discussed here, but obviously actually pausing is not an option.

We could 'snapshot' the state as it was at the time of an event, but that just
moves the problem down into the engine. That is, we've told the event/scripting
layer a lie about the true current state, and so when it says "given that the
state is X I want Y to happen" the state is no longer actually X, so should Y
happen or not?

On testing, it may be that we can introduce some testing hooks to alleviate
this problem, but I am not sure what they are. I don't think we should distort
normal operation in order to make it testable, however.

-- 
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, 8 March 2011 19:20:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 March 2011 19:20:41 GMT