Correct time, still the same problem :(

In Firefox the time shows without problem though...

and correct date?

yeap, correct time and date... the other problem is that in Firefox,within the game, the remaining time it shows is incorrect. when I click on "Board", it reloads, then it shows for a moment the correct remaining time in black (e.g., 0:45) and after half a second it shows , in red, a different **and wrong, longer!!** remaining time (in the example, 1:34).
That is not only a nuissance, but also very dangerous.

My browser (IE 9) does the black->red thing too, so I don't think that's a bug.
Sorry know nothing about chrome, but at a guess you should check where chrome gets its time reference from. Or just use firefox or IE9 (I know, I am the devil).

lol, well fiedler, the thing is that with chrome i have no time whatsoever, while in firefox i have half a second with the right time and then a false one.... is more like "chose your poison"...
oh, and all of this under windows 7....
(i have dual boot with ubuntu, i have to see what happens there with chromium)

Sounds like a bug pretty deep in the code. Just use IE9 and save yourself a lot of time. There are others ways to be a REBEL.

uh oh.... well i am not a rebel, i just happen to like wayyyyyy more the easiness of chrome and firefox.
Plus, well, you know, they are free, and IE is not.
And most important, i want some browser going the same way in both linux and windows. Not IE option for me there....
So, it is not about being a rebel...

Now, back on my question, what can i do to solve the timing problem?
And why there is such a problem?

try clearing your cache and cookies

be a REBEL. I'm just kidding :D

Yeah. I'm guessing it's a cache issue. The time reference, regardless of browser, comes from your computer time. Perhaps you have the wrong time cached.

The time you are seeing flash for a half second is what the server sends in UTC (Coordinated Universal Time). The java script in the browser then compares your timezone to UTC and adjusts the time for that. It then compares that against what your computer's clock says to see how much time is left.

I believe there is the potential that your computer's clock could show the correct time, but for the wrong timezone and that might cause something like this. So check your timezone too. If incorrect, then set it correctly and THEN set your clock correctly, and then check the website again.

As an example, let's say a game's phase is due to change at UTC 1am. You live in Britian with a timezone offset of UTC +0 so it should change at 1am your time too. But you moved there from the U.S. and had your timezone set to Pacific which is +8 and when you moved you just changed the clock instead of the timezone. So first the javascript adjusts the UTC 1am to 5pm Pacific. When you look at the game after 5pm, it thinks the time has come when it has not.

Hopefully it is that simple.

Although the cache issue is a real possibility as well.

kindofslow - you got me curious, so I installed chrome on my windows 7 machine - no time problems. I got it setup as my light-bandwidth browser, with shockwave/flash switched off. Goddamn vampires.