Closed Bug 370973 Opened 18 years ago Closed 15 years ago

wrong date (timezone) in google calendar & gmail

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Linux
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: hubert.muchalski, Unassigned)

Details

(Whiteboard: [CLOSEME 5-15-2010])

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20060601 Firefox/2.0.0.1 (Ubuntu-edgy) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20060601 Firefox/2.0.0.1 (Ubuntu-edgy) Ubuntu Edgy Eft (6.10), GNOME. In Gmail and Google Calendar the date/time shown don't match with system time/date. In other browsers (Konqueror) everything is shown correctly. In Epiphany (Gecko based browser) the problem is the same. Reproducible: Always Steps to Reproduce: 1.Use default build of Firefox (2.0.0.1) in Ubuntu Edgy (6.10) 2.Log into Google Calendar 3.Date/time don't match (about 24h ahead). e.g. Tuesday instead of Monday. Expected Results: Show date/time of system
Since the last tzdata update for Venezuela which changed the timezone from UTC-0400 to UTC-0430, most Javascript calendars and time scripts started to show an incorrect behavior. Calendars like [1] show tomorrow's date, just as Hubert stated, and some other calendars show a row of eight's on December 2007 (the date change ocurred on Dec 9th., 2007) The problem only happens on Javascript running on Gecko-based applications. For example, it appears on the mini-calendar of the Lightning plugin for Thunderbird, but not on the bigger calendar. Konqueror and other applications not related to Mozilla work flawlessly. [1] http://www.dynarch.com/projects/calendar/
The problem seems to be related to the timezone offset. The getUTC*() methods, such as getUTCDate() return the correct value on both Firefox 2.0.0.11 and Opera, Konqueror etc. However, the method getTimezoneOffset gives different values. My machine is using the timezone for Venezuela, which is UTC -4:30. getTimezoneOffset returns 270 on Konqueror, Opera and other browsers, and on Firefox 2.0.0.11 it returns -1170. Running strace shows that Firefox is reading /etc/localtime, so I suppose that it gets the timezone offset from this file.
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 5-15-2010]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.3 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.