Hi Ben,
Ben Sturmfels skribis:
> This does appear to be a privacy feature. To report the correct timezone
> offset, go to "about:config" and disable "privacy.resistFingerprinting" then
> restart IceCat.
Indeed. It would be nice if there was a setting specifically for the
timezone rather tha
On Fri, May 17, 2019 at 11:02, Ludovic Courtès wrote:
Hi Ben,
Ben Sturmfels 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().getTimez
On Fri, 17 May 2019, Ludovic Courtès wrote:
> Hi Ben,
>
> Ben Sturmfels 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().ge
Hi Ben,
Ben Sturmfels 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
