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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 17 May 2011 09:37:27 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QMGiV-0002ED-Bp@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #24 from David Singer <singer@apple.com> 2011-05-17 09:37:26 UTC ---
(In reply to comment #22)
> Please forgive me for repeating Philip, but Web apps with long-running HTML5
> tasks don't work. Even in an aggressive multiprocess, multithreaded browser
> implementation, such apps can't respond to user input or update any of their
> rendering apart from video (since browsers guarantee that only the state of the
> page between HTML5 tasks is rendered). The only way for an app to be responsive
> and stay in sync with other activity is to issue a series of very short-lived
> HTML5 tasks. That's why using one snapshot per task works well in practice.


You've just described a way to write buggy scripts (long-running tasks) that is
just as subtle as the original problem this thread started with (scripts that
don't base their actions on what the event indicated was true) or that came up
in discussion (scripts that ask for an event notification after it has
happened).

Time-based programming is not easy, and there are limited ways it can be made
so.

-- 
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, 17 May 2011 09:37:28 UTC

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