bug#35746: IceCat/Chromium timezone is wrong

[Ludovic Courtès]

Hi Ben,

Ben Sturmfels <address@hidden> 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’.