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

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

From: <bugzilla@jessica.w3.org>
Date: Sat, 16 Jul 2011 10:34:06 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qi2CE-0006Wt-6y@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #38 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2011-07-16 10:34:05 UTC ---
(In reply to comment #35)
> Could you enumerate exactly which features you think should be pinned?

All the media element state, at least.

This bug is asking that readyState and networkState be changed by the HTML task
that fires the event that signals the state change (before the event fires, of
course).

We can do something similar for the rest of the script-visible media element
state. Some of the HTML tasks that change media element state would not fire
DOM events of course, for example not every change to currentTime fires
timeupdate.

Beyond media elements, I would like to be able to say that in general, changes
to script-visible state other than those triggered by the script execution
itself are not observable during script execution, unless we have specific
reasons to make an exception. Usage of "new Date()" for timing script activity,
especially legacy usage, is a reasonable exception. New timing APIs under the
web-perf group may be another exception. There may be others.

-- 
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 Saturday, 16 July 2011 10:34:10 UTC

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