Subject: bug#35746: IceCat/Chromium timezone is wrong

From: Ludovic Courtès <[email-masked]>
Date: Fri, 17 May 2019 11:02:16 +0200

Hi Ben,

Ben Sturmfels <[email-masked]> skribis:

> Possibly completely unrelated, but noting that both icecat and chromium
> do this - which is wrong:
>
>> new Date().getTimezoneOffset()
> 0
>
> Where node does this - which is correct:
>
>> new Date().getTimezoneOffset()
> -600

I noticed it in IceCat and thought it might be a privacy feature.
But maybe it’s a genuine bug?

Ludo’.