Closed Bug 128125 Opened 23 years ago Closed 12 years ago

aol.com - browsertest doesn't understand date correctly

Categories

(Tech Evangelism Graveyard :: English US, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: timeless, Unassigned)

References

()

Details

(Whiteboard: [author])

The YearFromToday row results in Thu, 27 Jul 2000 05:00:00 UTC give or take .. [ie, nc4, moz, winEmbed]. It doesn't matter whether your clock is set correctly (my laptop has a y2002 problem).
Here's the problem: the variable |now| in their script is hard-coded: var now = new Date(99,6,28) In my timezone this is: Wed Jul 28 1999 00:00:00 GMT-0700 (Pacific Daylight Time) The results in their YearFromToday row read like this on my box: DATE METHOD YearFromToday now.getTime() + (24*60*60*1000*365) RESULT Thu, 27 Jul 2000 07:00:00 GMT So - this is basically correct, given the hard-coded value for |now|. It's just one day short. This is because 2000 happened to be a leap year, so the hard-coded value 24*60*60*1000*365 is one day too little ... I don't know why they hard-coded |now|; most testsuites do this: var now = new Date();
Blocks: 121236
Keywords: evang500
Summary: browsertest.web.aol.com doesn't understand date correctly → aol.com - browsertest doesn't understand date correctly
Looking for a tech contact...
contacted.
Status: NEW → ASSIGNED
Target Milestone: --- → Mar
tech evang june 2003 reorg
Status: ASSIGNED → NEW
Whiteboard: [author]
oops
Assignee: bc → english-us
Component: Authors → English US
QA Contact: mgalli → english-us
ain't gonna happen.
Target Milestone: Mar → Future
The bug is still here.
While the bug is indeed still there, it's just an issue in some test suite which looks limited and outdated anyway. I don't think we should spend time on finding a contact and passing on a fix at this point, and hope noone will disagree with me closing this bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.