From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [69.252.207.34]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 00A247A98D for ; Wed, 8 Apr 2015 06:21:44 -0700 (PDT) Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-02v.sys.comcast.net with comcast id DRKK1q0022AWL2D01RKsNR; Wed, 08 Apr 2015 13:19:52 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-04v.sys.comcast.net with comcast id DRKr1q0055LMg2101RKr95; Wed, 08 Apr 2015 13:19:51 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.3+ Date: Wed, 08 Apr 2015 09:19:51 -0400 Message-ID: <20150308091951.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1428499192; bh=volh9IyKud9GubrzgZCWRtWFvw+Sp/P80NQZrGcZ/WM=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=lbB1aYb47CVSUTclgHjBHDGk0ZuyAMlMIYwR4i5EyS12qMD0gTgYQvm7iEKFpsVVn NUXm1L8e4r0R4cA6UbFEiDYAiZ9V4z3r1CTEl2yQHywGMBouasZSrGNq7f1sJ6K+b8 Qtf4jN+GFoWOCPWBwCorlENhCM7CNFWBuKO7SvAweQN1zK3xTVko4j54B3OlIj5WF3 psFz/XB6i2rJtgNQgP61Vdeqjq9BnaPvAnRoJTD7sJvjKm8DaMwbcghtsOYma8y4ay x18NR6tYdsD9l9ccAMbUGyYyu07uOjhHeneoGMUzrqEG/xfshKefzoKTuO62K0o5N/ 8as2zBROzXhnA== Subject: [Edbrowse-dev] Short Timers X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2015 13:21:45 -0000 If you call up www.eventbrite.com you'll notice 10 javascript timers at the top of the page, all active in 4 milliseconds. It occurs to me that if javascript is suppose to run in 4 ms, it should probably just run. Now if js is scheduled to run in 10 seconds, then it should wait on your command, wait for you to read the page, because we read a new website slower than our sighted friends, so long timers are under our control, but perhaps any timer under one second, or whatever threshold we choose, should just run. Queue them up in order of time and run them. Even if they do nothing other than visual effects, at least those first ten annoying lines about js timers would be off of the web page. What do you think? Karl Dahlke