Few minor issues with Ajax version
-
On the whole the new ajax version works ok, but there are a few minor issues:
1. Can we please leave the widget digits blank until populated by ajax – looks weird when it gets the ajax time and it is way different from the values when the page was cached.
2. When it is not cached, the countdown time shown initially is 1 hour more than after the ajax call. This is because the php date calculations do not take into account DST for the target date but the JS functions do.
3. On my own server time is set to same as my local time, but I suspect that if my computer clock was in a different timezone, then all sorts of funny stuff would happen. But then again it might apply the local timezone several times which would balance out in the wash.
4. The clock does not keep good time i.e. if you open one tab now, and another tab in a few hours time, the countdown timers will not read the same. I suspect that this is because:
4a. the code doesn’t calculate the time difference every time it is called, but instead maintains a time difference which drifts cf the computer clock;
4b. the code does not set a repeating js timer, but instead uses a one-shot timer and then sets it again once it has displayed the new time – but the code takes time to run, so it is not called every 1000ms but (say) every 1025ms if the code takes 25ms to run.
In the big scheme of things these are all minor – the widget does count down and for the normal lifetime of a web page these are not important. But they are niggles.
- The topic ‘Few minor issues with Ajax version’ is closed to new replies.
