search

janodvarko / firecookie

Automatically exported from code.google.com/p/firecookie
Other
0 stars 3 forks source link

Local time for 'Expires' #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. whenever GMT+0 is odd

What is the expected output? What do you see instead?

Firefox Page Info show Expire time with respect to system timezone.
But Firecookie give no option but GMT.

What version of the product are you using? On what operating system?

Firecookie 0.6 / Firebug 1.2.06b / Firefox 3.0.1
OS: Win XP SP2 (en_US) | FreeBSD 7 | RHFC 5

Please provide any additional information below.

It would be better if firecookie / firebug provide more options.
GMT is not too bad, but localized timezone can be more convenient. 

I find the firecookie.js and s/toGMTString/toLocaleString/g .
So far this little hack satisfies my own need. 

Moreover, toGMTString()is deprecated in JS 1.2/1.3
Ref:
http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference:Global_Object
s:Date:toGMTString
Perhaps you will need to change to toUTCString() anyway.

Original issue reported on code.google.com by benc...@gmail.com on 29 Jul 2008 at 6:53

GoogleCodeExporter commented 9 years ago 
Another comment related to time format from Johnbo:
(from 
http://www.babelzilla.org/forum/index.php?showtopic=4494&st=0&p=43126&#entry4312
6)

When the column "Expires" shows a date, it's formatted in English format 
instead of
in local format. For example, I see "Wed, 01 Jan 2020 00:00:00 GMT" where I 
think I
should see "Mié, 01 Ene 2020 00:00:00 GMT" (in Spanish: Wednesday --> 
Miércoles;
January --> Enero). Furthermore, when I create a new cookie and I establish the
expiration date, it doesn't recognize the local format. I mean, in Spanish, 
dates are
almost always formatted as dd/mm/yyyy, but if I set the expiration date to 
13/08/2008
(what I thought it should be August 13th), it sets the cookie expiration to 
"Wed 07
Jan 2009 23:00:00 GMT". If this can't be fixed, at least it could warn me 
saying that
I'm entering an invalid month (13).

Original comment by odva...@gmail.com on 19 Aug 2008 at 8:08

GoogleCodeExporter commented 9 years ago 
Javascript 1.5 ( Hmm, perhaps even 1.8 ) does not provide std lib for l10n 
date/time
format support, AFAIK. If you don't mind, please take reference from Dao 
Gottwald 
<dao at design-noir.de>:
http://en.design-noir.de/webdev/JS/Date.format/

Several western lang l10n are included.

Original comment by benc...@gmail.com on 19 Aug 2008 at 8:37

GoogleCodeExporter commented 9 years ago 
Part of the bug is fixed. The expires time displayed in the cookie list 
respects  the
current locale. Just like the Firefox Cookies dialog does (r14).
Honza

Original comment by odva...@gmail.com on 22 Aug 2008 at 3:10

GoogleCodeExporter commented 9 years ago 
There are new date and time pickers (new UI widgets) in the edit-cookie dialog. 
The
user can also set the cookie expire-time using the local (and localized) 
timezone.

Both XUL elements <datepicker> and <timepicker> are introduced in Firefox 3 so, 
the
dialog remains the same in older versions of Firefox.

Committed in trunk (r22)

Honza

Original comment by odva...@gmail.com on 2 Sep 2008 at 6:06

GoogleCodeExporter commented 9 years ago 
I believe that this bug is fixed in v0.7 (beta). 
http://www.softwareishard.com/blog/firebug/firecookie-07-beta/
Please, let me know if there would be any problem.
Honza

Original comment by odva...@gmail.com on 9 Sep 2008 at 7:53