On Wed, 22 Apr 2020, Ben Sturmfels wrote:
> One additional note that may help others diving into this issue. I found that
> disabling "privacy.resistFingerprinting" immediately changed the result of
> `new
> Date().toString()` on all tabs, but `new Date().getTimezoneOffset()` was
> changed
>
One additional note that may help others diving into this issue. I
found that disabling "privacy.resistFingerprinting" immediately changed
the result of `new Date().toString()` on all tabs, but `new
Date().getTimezoneOffset()` was changed only on the about:config tab.
After a restart all tabs
Hi Mark,
Thanks for responding.
It appears that this behavior is controlled by the
privacy.resistFingerprinting option.
Setting it to false solves the problem on IceCat for the desktop,
but the problem persists on IceCatMobile (Android), regardless of the
option.
(Even after clearing the app's
Hi Jelle,
Jelle Geerts writes:
> var s1 = new Date().toString();
> var s2 = new Date().toLocaleString();
> var s3 = new Date().toLocaleString('nl', {'timeZone': 'Europe/Amsterdam'});
>
> The resulting strings were:
> s1 === 'Fri Jun 07 2019 13:58:32 GMT+ (UTC)'
> s2 === '6/7/2019,
var s1 = new Date().toString();
var s2 = new Date().toLocaleString();
var s3 = new Date().toLocaleString('nl', {'timeZone': 'Europe/Amsterdam'});
The resulting strings were:
s1 === 'Fri Jun 07 2019 13:58:32 GMT+ (UTC)'
s2 === '6/7/2019, 1:58:32 PM'
s3 === '7-6-2019 15:58:32'
s1 is not
