Bug 1826998 Comment 12 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Here's a screencast with an extended version of the steps in comment 11.

I enable `resistFingerprinting`, and then `setTZtoUTC`, and then I disable `resistFingerprinting`, and then re-enable `resistFingerprinting`.  Between each change, I do `new Date()`.  In ever case, I evaluate `new Date()`.  They all show PDT (my local timezone) except at the very end, when I've (re)-enabled `resistFingerprinting` **while the setTZtoUTC pref was enabled**.
Here's a screencast with an extended version of the steps in comment 11.

I enable `resistFingerprinting`, and then `setTZtoUTC`, and then I disable `resistFingerprinting`, and then re-enable `resistFingerprinting`.  Between each change, I do `new Date()`.  In ever case, I evaluate `new Date()`.  They all show PDT (my local timezone) except at the very end, when I've (re)-enabled `resistFingerprinting` **while the setTZtoUTC pref was enabled** -- that one shows the datestamp in Coordinated Universal Time.
Here's a screencast with an extended version of the steps in comment 11.

I enable `resistFingerprinting` (t=5s), and then `setTZtoUTC` (t=10s), and then I disable `resistFingerprinting` (t=15s), and then re-enable `resistFingerprinting` (t=20s).  Between each change, I evaluate `new Date()` in the console.  They all show PDT (my local timezone) except at the very end, when I've (re)-enabled `resistFingerprinting` **while the setTZtoUTC pref is enabled** -- that one shows the datestamp in Coordinated Universal Time.
Here's a screencast with an extended version of the steps in comment 11.

I enable `resistFingerprinting` (t=5s), and then `setTZtoUTC` (t=10s), and then I disable `resistFingerprinting` (t=15s), and then re-enable `resistFingerprinting` (t=20s).  Between each change, I evaluate `new Date()` in the console.  They all show PDT (my local timezone) except at the very end, when I've (re)-enabled `resistFingerprinting` **with the setTZtoUTC pref being enabled at that moment of re-enabling** -- that one shows the datestamp in Coordinated Universal Time.  So our behavior seems to depend on the order in which you enable the prefs.
Here's a screencast with an extended version of the steps in comment 11.

I enable the prefs for `resistFingerprinting` (t=5s), and then for `setTZtoUTC` (t=10s), and then I disable `resistFingerprinting` (t=15s), and then re-enable `resistFingerprinting` (t=20s).  Between each change, I evaluate `new Date()` in the console.  They all show PDT (my local timezone) except at the very end, when I've (re)-enabled `resistFingerprinting` **with the setTZtoUTC pref being enabled at that moment of re-enabling** -- that one shows the datestamp in Coordinated Universal Time.  So our behavior seems to depend on the order in which you enable the prefs.
Here's a screencast with an extended version of the steps in comment 11.

I enable the prefs for `resistFingerprinting` (t=5s), and then for `setTZtoUTC` (t=10s), and then I disable `resistFingerprinting` (t=15s), and then re-enable `resistFingerprinting` (t=20s).  Between each change, I evaluate `new Date()` in the console.  They all show PDT (my local timezone) except at the very end, when I've (re)-enabled `resistFingerprinting` **with the setTZtoUTC pref being already-enabled at the moment that resistFingerprinting becomes enabled** -- that one shows the datestamp in Coordinated Universal Time.  So our behavior seems to depend on the order in which you enable the prefs.
Here's a screencast with an extended version of the steps in comment 11.

I enable the prefs for `resistFingerprinting` (t=5s), and then for `setTZtoUTC` (t=10s), and then I disable `resistFingerprinting` (t=15s), and then re-enable `resistFingerprinting` (t=20s).  Between each change, I evaluate `new Date()` in the console.  They all show PDT (my local timezone) except at the very end, when I've (re)-enabled `resistFingerprinting` **with the setTZtoUTC pref being already-enabled at the moment that resistFingerprinting becomes enabled** -- that one shows the datestamp in Coordinated Universal Time.  So our behavior seems to depend on the order in which you enable the prefs (and particularly on whether `setTZtoUTC` is enabled or disabled at the moment `resistFingerprinting` becomes enabled).

Back to Bug 1826998 Comment 12