W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2009

[Bug 7843] Please make 'abort', ' loadend' and 'emptied' use "queue a task". Firing them sync is annoying to implement and doesn't seem to solve any problem.

From: <bugzilla@wiggum.w3.org>
Date: Tue, 20 Oct 2009 11:14:53 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1N0Cg1-0002SC-Ir@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7843


Philip Jägenstedt <philipj@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simonp@opera.com




--- Comment #3 from Philip Jägenstedt <philipj@opera.com>  2009-10-20 11:14:53 ---
I'd like to reopen this bug, but can't see an option to do that (probably need
an admin account).

All other events on media elements are async with the actual state and cannot
be trusted. In the case of 'abort' and 'emptied' ('loadend' is no more) the
state of the media element is reset before firing them, so there is nothing
there which scripts could reasonably depend on.

The main reason I'd like these events to be async is because it would be much
easier to implement with all events being treated equally. In an interruptable
ECMAScript engine synchronous (from the scripts point of view) event handling
requires saving all state and waiting for the handler to finish before
continuing. It can be done, but it's annoying and it would be nice if there
were a compelling reason to do it.


-- 
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, 20 October 2009 11:14:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 October 2009 11:14:57 GMT