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 20:17:58 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PxmJ4-0003bl-3G@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #9 from David Singer <singer@apple.com> 2011-03-10 20:17:57 UTC ---
On the example problem:
v.onloadstart = function() {
  v.currentTime = 10;
}
I would say that this is an *obvious* bug -- the action of a function should
only depend on what's assured by the event that the function runs in response
to. Loadstart does not assure seekability.

Now, if this were true, but somehow the state regressed between the event
firing and the function running (perhaps something else changed the URL on the
video element, for example), then that's more like the races that can happen.

Freezing is not appropriate, as we all recognize; and snapshot means that
scripts are using state/values that are old, and then asking for action based
on that. is currentTime one of the snapshotted values?  If so, is timeofday
also snapshotted, so we can see how well we are playing in real-time? And so
on...

-- 
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 20:17:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 March 2011 20:17:59 GMT