[Greasemonkey] Storing large integers with GM_setValue overflows?

[Matthias Bauer]

On 29.06.2005 19:50 Matthias Bauer wrote:

>> Yeah, I would image that should definitely work. If it isn't perhaps
>> some underlying limitation on the XPCOM preferences object (which
>> would suck).
> 
> It's stored as integer. app.update.lastUpdateDate is set to 1119994042
> (integer), so it probably is not an XPCOM limitation.

Never mind, lastUpdateDate uses seconds, but Date.getTime() returns
milliseconds. Division by 1000 prior to setValue should solve the
problem for me.

-Matt