Bug 1826998 Comment 0 Edit History

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

Original comment by
on 
STR:
1. Set about:config pref `privacy.resistfingerprinting` to `true`
2. Restart Firefox.
3. Open web console (ctrl shift k) and type `new Date()`
4. Try that again but now explicitly stringify: `(new Date()).toString()`

ACTUAL RESULTS:
`new Date()` gets shown in devtools with your local timzone, implying that that's what its stringified/etc. version will be, and implying that the date has your timezone encoded in it.

EXPECTED RESULTS:
The date should probably be shown in UTC, since I think that's how we have it encoded to reduce fingerprinting.
Revision 1 by
on 
STR:
1. Set about:config pref `privacy.resistfingerprinting` to `true`
2. Restart Firefox.
3. Open web console (ctrl shift k) and type `new Date()`
4. Try that again but now explicitly stringify: `(new Date()).toString()`

ACTUAL RESULTS:
`new Date()` gets shown in devtools with your local timzone, implying that that's what its stringified/etc. version will be, and implying that the date has your timezone encoded in it.

(In contrast, `(new Date()).toString()` reports the date in UTC as-expected.)

EXPECTED RESULTS:
The date should probably be shown in UTC, since I think that's how we have it encoded to reduce fingerprinting.
Revision 2 by
on 
STR:
1. Set about:config pref `privacy.resistfingerprinting` to `true`
2. Restart Firefox.
3. Open web console (ctrl shift k) and type `new Date()`
4. Try that again but now explicitly stringify: `(new Date()).toString()`

ACTUAL RESULTS:
`new Date()` gets shown in devtools with your local timzone, implying that that's what its stringified/etc. version will be, and implying that the date has your timezone encoded in it.

(In contrast, `(new Date()).toString()` reports the date in UTC as-expected.)

EXPECTED RESULTS:
The response to `new Date()` should probably be shown in UTC, since I think that's how we have it encoded to reduce fingerprinting.
Revision 3 by
on 
STR:
1. Set about:config pref `privacy.resistFingerprinting` to `true`
2. Restart Firefox.
3. Open web console (ctrl shift k) and type `new Date()`
4. Try that again but now explicitly stringify: `(new Date()).toString()`

ACTUAL RESULTS:
`new Date()` gets shown in devtools with your local timzone, implying that that's what its stringified/etc. version will be, and implying that the date has your timezone encoded in it.

(In contrast, `(new Date()).toString()` reports the date in UTC as-expected.)

EXPECTED RESULTS:
The response to `new Date()` should probably be shown in UTC, since I think that's how we have it encoded to reduce fingerprinting.
Revision 4 by
on 
STR:
1. Set about:config pref `privacy.resistFingerprinting` to `true`
2. Restart Firefox.
3. Open web console (ctrl shift k) and type `new Date()`
4. Try that again but now explicitly stringify: `(new Date()).toString()`

ACTUAL RESULTS:
`new Date()` gets shown in devtools with your local timezone, implying that that's what its stringified/etc. version will be, and implying that the date has your timezone encoded in it.

(In contrast, `(new Date()).toString()` reports the date in UTC as-expected.)

EXPECTED RESULTS:
The response to `new Date()` should probably be shown in UTC, since I think that's how we have it encoded to reduce fingerprinting.

Back to Bug 1826998 Comment 0