27 Nov '14, 11am

For any JavaScripters who don't know: DON'T TRUST SETINTERVAL TIMING. Especially in inactive tabs. #JS

Do your Jasmine tests (or anything else) seem to lock up when they aren’t the active tab in your browser? Unfortunately, your new and modern browser is to blame. There are a few workarounds, but none of them are ideal in my opinion. The cause of the problem In early 2011, both Firefox and Chrome clamped the minimum wait time for setTimeout and setInterval to one second when running in a tab that is not the active tab for its window . You might also be surprised to find out that HTML5 specifies a minimum of 4ms delay for setTimeout . Workarounds Workaround 1: Run that tab in its own window This is the easiest solution, but it’s often less convenient to switch between browser windows when you want to just switch between tabs in the same window. Workaround 2: Compensate for the fact that your callbacks will happen at most once per second The accepted answer at this StackOverf...

Full article: http://pivotallabs.com/chrome-and-firefox-throttle-settim...

Tweets

Keep Tabs on Passing Jets with Pi and SDR

Keep Tabs on Passing Jets with Pi and SDR

hackaday.com 27 Nov '14, 9pm

Obviously Software Defined Radio is pretty cool. For a lot of hackers you just need the right project to get you into it. ...

Mozilla to Add “One-Click Searches” to Firefox

searchenginewatch.com 26 Nov '14, 5am

Just less than a week after it revealed a new royalty agreement with Yahoo , Mozilla says it will release a number of new ...