W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

RE: solving the CPU usage issue for non-visible pages

From: Ennals, Robert <robert.ennals@intel.com>
Date: Wed, 21 Oct 2009 19:26:38 +0100
To: Maciej Stachowiak <mjs@apple.com>
CC: Jonas Sicking <jonas@sicking.cc>, "robert@ocallahan.org" <robert@ocallahan.org>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <EB332302649177439359CE520D92A0AF9F3969A2@irsmsx503.ger.corp.intel.com>
[hoping that quoting works better this time]

On Oct 20, 2009, at 7:41 PM, Maciej Stachowiak wrote:
> On Oct 20, 2009, at 7:13 PM, Ennals, Robert wrote:
> > I'd even be tempted to risk breaking existing applications a little bit and make the
> > *default* behavior for HTML5 pages be that "time stops" when a page is not visible. 
> > If a programmer has a good reason to run javascript on an invisible page then they 
> > should have to pass an option to make it clear that they know what they are doing.
> One challenge with this approach is that there's no good way at present to make time stop for a > plugin. I suspect more generally that this approach would cause compatibility bugs.

Yeah. I expect this would break some stuff. It could be useful to think about what people might be doing that could be broken, so we can see if there is an easy solution.

Are you aware of any common patterns in which a plugin communicates with javascript in such a way that the app would stop working if javascript timer events stopped firing for a while?

My hunch is that the general problem of "javascript doesn't run for a while" (in the absence of plugins) shouldn't break many web sites, since this is already what happens when a computer goes to sleep. OTOH there is probably something I'm missing.

Received on Wednesday, 21 October 2009 18:27:48 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:20 UTC