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:12:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pxo5X-0001Xn-Mw@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #10 from Philip Jägenstedt <philipj@opera.com> 2011-03-10 22:12:04 UTC ---
(In reply to comment #9)
> 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.

That it's an obvious bug doesn't change the fact that the behavior is
unreliable. Unless the spec defines the behavior, web authors will inevitably
come to depend on the most common behavior in the browsers they test in,
because they develop by trial and error. Do you not think that this is a real
risk?

> 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...

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. Do you find
this objectionable? If so, what concrete problems would it cause?

The best behavior of currentTime isn't obvious, I'll agree thus far. Are there
any use cases for scripts observing currentTime changes while they are running?
If not, what concrete problems would freezing it (like Firefox, presumably)
cause?

-- 
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:12:09 GMT

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