Thanks for the post Kim.

>>This is just a wild guess, it really should work the way you have it set up
>>(I have the same clock settings in my original preferences.js, and it works fine).
>>But fact is that 1000 / 60 = 16.66666667, so if values in localprefs are
>>interpreted as seconds rather than milliseconds, your clock would update
>>once every 17 minutes.
>>That sounds really far-fetched, though -- just a guess.
>>Also, my clocktooltipform = "", I'm not sure what happens if you set it
>>to false... Does JScript coerce it into a string?
I tried setting clocktooltipform = "" just in case. My clock has said 14:04 since I logged on a while ago. It's currently 14.41. It sounds like no one else has experienced this bug.
 
Cheers, Tom.

Reply via email to