On Tue, Oct 20, 2009 at 7:13 PM, Ennals, Robert robert.enn...@intel.com wrote:
On Tuesday, October 20, 2009 at 5:37 PM, Jonas Sicking jo...@sicking.cc
wrote:
On Tue, Oct 20, 2009 at 4:44 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Wed, Oct 21, 2009 at 11:59 AM, Ennals, Robert
On Wed, Oct 21, 2009 at 5:16 AM, Robert O'Callahan wrote:
There are lots of reasons why the browser might deduce that the user is not
paying attention to a document, e.g.
-- the browser window containing the document is minimized
-- the tab containing the document is hidden
-- the document
I like window.hasAttention if you can even vaguely define what it
means... It's pointless to make it so vague that useful things will
work differently in different browsers by accident rather than by
design (for example, it might be ok for mobile devices to work
differently by design, but it would
usage issue for non-visible pages
So... in describing this feature:
Is it really the visibility of the page that is being queried - or the
some kind of state of a window? Maybe it's a silly bit of semantics,
but it seems clearer to me that most of the things discussed here are
about a whole
So.. I wound up speaking to Robert offline and in our discussion his
comments became much clearer to me and I think that it's at least
worth documenting in case anyone else misunderstands as I did (even
historically via the archive).
There are really a few proposals here which are sort of only
So... in describing this feature:
Is it really the visibility of the page that is being queried - or the
some kind of state of a window? Maybe it's a silly bit of semantics,
but it seems clearer to me that most of the things discussed here are
about a whole window/tab being minimized (either to
I suppose I should not have used that phrasing... It wasn't really
accurate and it obscures my point... My point was that I actually
wanted it to run in the background... So - does time stop, or just
rendering? I think that you have to be very clear.
On Tue, Oct 20, 2009 at 8:43 PM, Robert
[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:
[snip]
I'd even be tempted to risk breaking existing applications a little bit and
make the
*default* behavior for HTML5 pages be that time
On Wed, Oct 21, 2009 at 11:59 AM, Ennals, Robert robert.enn...@intel.comwrote:
Should we also consider the case where a web site wants to keep its
interface up to date with some server state and is using up CPU time and
network resource to do so?
You could abuse my proposal to do this, by
On Tue, Oct 20, 2009 at 4:44 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Wed, Oct 21, 2009 at 11:59 AM, Ennals, Robert robert.enn...@intel.com
wrote:
Should we also consider the case where a web site wants to keep its
interface up to date with some server state and is using up CPU
On Tuesday, October 20, 2009 at 5:37 PM, Jonas Sicking jo...@sicking.cc
wrote:
On Tue, Oct 20, 2009 at 4:44 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Wed, Oct 21, 2009 at 11:59 AM, Ennals, Robert
robert.enn...@intel.com
wrote:
Should we also consider the case where a web
On Oct 20, 2009, at 7:13 PM, Ennals, Robert wrote:
One thing I like about the requestAnimationFrame approach is that
it makes it easy to do the right thing. If the simplest approach
burns CPU cycles, and programmers have to think a bit harder to
avoid doing this, then I suspect the
On Wed, Oct 21, 2009 at 3:41 PM, Maciej Stachowiak m...@apple.com wrote:
On Oct 20, 2009, at 7:13 PM, Ennals, Robert wrote:
One thing I like about the requestAnimationFrame approach is that it
makes it easy to do the right thing. If the simplest approach burns CPU
cycles, and programmers
; Jonas Sicking; rob...@ocallahan.org; public-
weba...@w3.org
Subject: Re: solving the CPU usage issue for non-visible pages
So... in describing this feature:
Is it really the visibility of the page that is being queried - or the
some kind of state of a window? Maybe it's a silly bit
On Wed, Oct 21, 2009 at 3:57 PM, Brian Kardell bkard...@gmail.com wrote:
Is it really the visibility of the page that is being queried - or the
some kind of state of a window? Maybe it's a silly bit of semantics,
but it seems clearer to me that most of the things discussed here are
about a
On Wed, Oct 21, 2009 at 4:34 PM, Brian Kardell bkard...@gmail.com wrote:
For example, I recently the Image Evolution demo from
http://www.canvasdemos.com/2009/07/15/image-evolution/ as a kind of a
performance test and let it run for three days - during which it was
not visible 99.999% of the
I posted something about this in the whatwg list and was told to bring it
here.
Currently, AFAIK, the only way to do animation in HTML5 + JavaScript is
using setInterval. That's great but it has the problem that even when the
window is minimized or the page is not the front tab, JavaScript has no
FYI, the original WhatWG thread:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/thread.html#23625
On Mon, Oct 19, 2009 at 1:51 PM, Gregg Tavares g...@google.com wrote:
I posted something about this in the whatwg list and was told to bring it
here.
Currently, AFAIK, the only
I have a proposal for solving this here:
http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/527d0cedb9b0df7f/57625c94cdf493bf
The gist is very simple:
1) window.requestAnimationFrame(): Signals that an animation is in progress,
and requests that the browser schedule a
19 matches
Mail list logo
