Issue 792: TRACKING: Chrome does not implement the Webkit 10ms setTimeout clamp. http://code.google.com/p/chromium/issues/detail?id=792
Comment #7 by [EMAIL PROTECTED]: Found the first major website which has a bug due to 0ms timers: http://www.nytimes.com/2008/09/16/business/16paulson.html?hp The problem is that they include the prototype.js module twice and it sets off two setInterval timers to poll for the page being loaded. Since it doesn't expect two concurrently to be running, the logic for clearing the timer doesn't work. I notified NYT and also filed a defensive coding fix with prototype: http://prototype.lighthouseapp.com/projects/8886/tickets/346-nytimes-on-safari-error-with-double-included-prototypejs -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
