Closed
Bug 359248
Opened 18 years ago
Closed 17 years ago
minimo returns wrong time in javascript applications such as google personalized page
Categories
(Minimo Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: minimo, Assigned: dougt)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows CE 5.1; nv:1.8.1) Gecko/20061102 Minimo/0.016 recent minimo nightly releases think my machine time is set for GMT+1600 when in fact it is set for GMT-0800. I first noticed this problem when I accessed my google calendar and saw that the highlighted date was 24hrs in the future. Reproducible: Always Steps to Reproduce: 1.Set up Google personalized home page to display google calendar widget. 2.Make sure both calendar and ipaq 4705 are set to GMT-0800 3.Access page using minimo nightly build. 4.Date 16 hours in the future is highlighted on calendar. 5.To explore this further I ran the following javascript in both Minimo and Opera Mobile: <script type="text/javascript"> document.write(Date()) </script> Actual Results: Minimo returns: Wed Nov 01 2006 10:24:42 GMT+1600 Opera returns: Tue 31 Oct 2006 10:24:42 GMT-0800 Expected Results: Minimo should have returned date/time equal to that set on WM5 device, GMT-0800. tested on ipaq 4705 running WM5 rom 2.01. Would this bug cause minimo to misread pages in the cache as out of date?
Reporter | ||
Updated•18 years ago
|
OS: All → Windows CE
Hardware: All → PocketPC
Reporter | ||
Comment 1•17 years ago
|
||
Still evident in minimo 0.2
Assignee | ||
Comment 2•17 years ago
|
||
minimo component is now closed and the minimo project isn't going to be supported. New work has started on a new mobile effort. Please see schrep's posting for more info. We hope you will be involved. http://weblogs.mozillazine.org/schrep/archives/2007/10/mozilla_and_mobile.html
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•