Date hooks fail for meta-refresh?
It is possible that some meta-refresh based logins are able to cause the date hooking code to believe that the hooks ran where as in fact they did not. This seemed to happen on one login to my google summer of code mentor account, which sets the TZ cookie to the number of minutes you are offset from UTC.
The problem is this is very difficult to reproduce. It is likely not just a meta-refresh login, but also a race condition that depends on the speed at which the meta-refresh reloads the page..
I will be adding some code to double check both directions of date hooks for all LocationChange progress events to detect this bug and at least alert the user somehow if its occurence is detected.
[Automatically added by flyspray2trac: Operating System: All]