Closed Bug 272411 Opened 17 years ago Closed 12 years ago

calDateTime.jsDate doesn't handle timezones correctly

Categories

(Calendar :: Internal Components, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: shaver, Unassigned)

References

Details

Attachments

(2 files)

Now that I fixed .jsDate:

js> b.jsDate = new Date()
Tue Nov 30 2004 08:18:16 GMT-0500 (UTC)
js> b.jsDate
Thu Dec 30 2004 13:18:16 GMT-0500 (UTC)

Looks like it's giving me back GMT, but not changing the timezone to GMT-0000. 
Or something.
Blocks: caldav
putenv("TZ=") doesn't do what is really wanted here.  The latest version of
libical uses putenv("TZ"), which should (I think) work.
though I just not realize that this patch won't fix the bug you report here;
that's a separate (shortly-to-be-fixed) issue
Comment on attachment 167584 [details] [diff] [review]
272411-libical-timezone-horkage-0.patch

It might be a good time to update libical altogether to their latest and
greatest from cvs,( Bug 237302 ), preserving our patches of course.
QA Contact: vladimir → base
Is this still valid?
Depends on: 394902
WORKSFORME
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Verified with todays nightly builds.
Status: RESOLVED → VERIFIED
Flags: in-testsuite?
Attached patch Test - v1Splinter Review
The test is quite simple. It uncovered that we don't save milliseconds in calIDateTime, but I don't think thats a must.
Attachment #414004 - Flags: review?(mschroeder)
Comment on attachment 414004 [details] [diff] [review]
Test - v1

r=mschroeder
Attachment #414004 - Flags: review?(mschroeder) → review+
Test checked in on cc rev d31389c77e0c and c191 rev b1e0280e9865
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.