Issue 792: TRACKING: Chrome does not implement the Webkit 10ms setTimeout clamp. http://code.google.com/p/chromium/issues/detail?id=792
Comment #2 by [EMAIL PROTECTED]: I checked into the scripts at bobkush.com and dynamicdrive.com. Both are basically the same script. The easy fix is to change the setTimeout() to a larger value; using setTimeout(0) is not necessary. A better fix is to not use setTimeout and instead use the body onScroll event (works on FF, Webkit, IE). This has two benefits: First, it fixes the CPU issue, but secondarily (for Chrome) it removes the flicker which is pretty nasty when using either form of setTimeout(). Tests: http://www.belshe.com/test/menu-setTimeout.html http://www.belshe.com/test/menu-onScroll.html -- 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 -~----------~----~----~----~------~----~------~--~---
