From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Sturmfels Subject: bug#35746: IceCat/Chromium timezone is wrong Date: Wed, 22 Apr 2020 23:43:58 +1000 Message-ID: <87zhb3bppd.fsf@sturm.com.au> References: <8736lfrh6y.fsf@sturm.com.au> <87y336hct1.fsf@gnu.org> <87v9yasgkd.fsf@sturm.com.au> <87d0khzc6f.fsf_-_@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:37574) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRFgU-0006a2-S1 for bug-guix@gnu.org; Wed, 22 Apr 2020 09:45:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jRFgU-00059R-6k for bug-guix@gnu.org; Wed, 22 Apr 2020 09:45:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40084) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jRFgT-00058K-Qn for bug-guix@gnu.org; Wed, 22 Apr 2020 09:45:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jRFgT-0004yA-Np for bug-guix@gnu.org; Wed, 22 Apr 2020 09:45:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87d0khzc6f.fsf_-_@gnu.org> ("Ludovic =?UTF-8?Q?Court=C3=A8s?="'s message of "Fri, 17 May 2019 11:02:16 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: 35746@debbugs.gnu.org On Fri, 17 May 2019, Ludovic Court=C3=A8s 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().getTimezoneOffset() >> -600 > > I noticed it in IceCat and thought it might be a privacy feature. > But maybe it=E2=80=99s a genuine bug? > > Ludo=E2=80=99. This does appear to be a privacy feature. To report the correct timezone of= fset, go to "about:config" and disable "privacy.resistFingerprinting" then= restart IceCat. Note that toggling "privacy.resistFingerprinting" immediately changed the r= esult of `new Date().toString()` on all tabs, but `new Date().getTimezoneOf= fset()` was changed only on the about:config tab. After a restart all tabs showed the correct o= ffset. See this IceCat bug report discussion: https://lists.gnu.org/archive/html/bug-gnuzilla/2019-06/msg00010.html Regards, Ben