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

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Aug 2011 21:36:20 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qo09s-0001aq-E4@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #45 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-01 21:36:19 UTC ---
Preventing the video from playing until the events have been processed seems
like building latency into the design. Event dispatch can sometimes be delayed
quite a lot, e.g. if there's a lot of activity going on. Are we sure we want to
be introducing this kind of latency?

The spec does currently delay a number of transitions until stable states (i.e.
til the end of the current event loop task), e.g. .seeking only changes in this
way, and most networkState transitions are done in stable states. I could go
through the spec and see if there's any other transitions that could be made
more stable. I don't know that readyStates would make sense done this way
though. There's no point readyState saying there's FUTURE_DATA when the video
has actually ended. Similarly, it's not like you can actually prevent the video
from ending before it's ended. The video ends when you run out of material,
regardless of how busy the browser is.

-- 
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 Monday, 1 August 2011 21:36:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:15 UTC