Hi Peter,
On Oct 2, 2008, at 6:28 PM, Peter Kasting wrote:
On Thu, Oct 2, 2008 at 3:23 AM, Rob Burns <[EMAIL PROTECTED]> wrote:
As another drastic anecdotal step, I've turned off javascript on
Safari (my main browser) and turn to other browsers when I find a site
that requires javascript. If I don't do that, I find my Macbook Air
battery eaten away in under an hour just because I left pages open
that use setTimeout inappropriately.
Safari doesn't have a lower setTimeout() cap than Firefox, so I
don't think this data point is meaningful.
This wasn't a comparison of the handling of different browsers. I was
saying that this is a rather drastic measure that users have to take
in order to avoid errant javascripts from eating away battery storage.
It might make sense to allow users to disable timers separately from
disabling javascript in total. In that way it might also encourage
authors to use timers appropriately when they might not be able to
count on timers being enabled always (using them only when appropriate
then).
Take care,
Rob
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
