timeout = timeout < 10 ? 10 : timeout;
Read today on WebKit’s Surfin’ Safari blog (emphasis mine):
Some Web pages specify repeating timers with an extremely small timeout. In fact they often use the value 0 to mean “Fire as soon as you can.” Safari 2 does not throttle these timeouts, and so a poorly-constructed page that specifies a repeating timer under 10ms will actually hog a lot of CPU. Aggressive timers were actually a problem in Mozilla for a long time before being fixed, and they are currently a problem in Safari 2. WinIE, Firefox, and WebKit nightlies basically error-correct the badly constructed page and ignore timer values of < 10ms by changing them to be 10ms.
That’s defintely something I wasn’t aware of. Not that I have any utility for a timer set below 10ms myself.
Comments
-
says:
That’s true even for very “realtimey” stuff, like effects. For example the script.aculo.us effects engines uses a 15ms interval which equates to a maximum framerate of ~66fps.
Thu, March 01 at 11:57 AM
-
says:
Well Thomas,
Effects lib is the first thing I thought about when I read about this. But when you you think about it, that still means that you can go down to a rate of 100 fps, which is far more that what the human eye needs to have the illusion of movement (movies run at 24 fps, as far as I know).
So this is really a non-issue, just an interesting fact.
Might be something to keep in mind when setting timeouts to deal with browser rendering issues though.
Thu, March 01 at 14:22 PM
