J
John Geddes
I have two XP PCs - both set for the timezone "GMT (Dublin...London)"
with Daylight Saving ON. (We are current on GMT+1 here).
But they are an hour different in the local time shown on the page
http://wwp.greenwichmeantime.com and as read by JavaScript in a test
webpage that I have written. That makes me suspect XP
rather than Javascript.
Both PC's show the correct local time in the Systray area, and this is
confirmed if I force an "Update Now" on the Internet Time tab. They both
report correct times for file changes.
The problem PC (XP Pro) is reading time in Javascript as if it has Time
Zone locked to Greenwich and Daylight Saving OFF. It reports
date.getTimezoneOffset() - which should give the -60 minutes between
local time and GMT - as Zero. And it gives the same offset for today's
date and for a date in February (should be different). I've change
timezones and Daylight Savings settings - and whilst the Systray clock
changes, the time reported by Javascript stays the same - GMT+0 every
time. Restarting makes no difference.
The OK PC (XP Home) has all the same settings, but this one behaves
fine on exactly the same test webpage. It reports
date.getTimezoneOffset() as -60 for now, and zero for
February. Change the timezone and the reported offset changes accordingly.
Has anyone experienced the same? Is there any Registry setting I should
be checking?
John Geddes
England
with Daylight Saving ON. (We are current on GMT+1 here).
But they are an hour different in the local time shown on the page
http://wwp.greenwichmeantime.com and as read by JavaScript in a test
webpage that I have written. That makes me suspect XP
rather than Javascript.
Both PC's show the correct local time in the Systray area, and this is
confirmed if I force an "Update Now" on the Internet Time tab. They both
report correct times for file changes.
The problem PC (XP Pro) is reading time in Javascript as if it has Time
Zone locked to Greenwich and Daylight Saving OFF. It reports
date.getTimezoneOffset() - which should give the -60 minutes between
local time and GMT - as Zero. And it gives the same offset for today's
date and for a date in February (should be different). I've change
timezones and Daylight Savings settings - and whilst the Systray clock
changes, the time reported by Javascript stays the same - GMT+0 every
time. Restarting makes no difference.
The OK PC (XP Home) has all the same settings, but this one behaves
fine on exactly the same test webpage. It reports
date.getTimezoneOffset() as -60 for now, and zero for
February. Change the timezone and the reported offset changes accordingly.
Has anyone experienced the same? Is there any Registry setting I should
be checking?
John Geddes
England