JS new date show wrong timezone
Categories
(Core :: JavaScript Engine, defect, P1)
Tracking
()
People
(Reporter: homertreddi, Assigned: anba)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0
Steps to reproduce:
1.display a javascript new date onto a web page (any)
2.change timezone on computer
3.display date again, it will not match computer timezone
4.Do the same procedure on the Chrome browser to see the date in the correct format set on the computer
Actual results:
If i visit web pages with new Date() function, i see the current timezone set on local computer.
If i change computer time zone and refresh web page, i continue to see old time with old time zone.
If i try same procedure on other browser like Chrome, the web page return correct datetime timezone
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::JavaScript Engine' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Assignee | ||
Comment 2•3 years ago
|
||
Neither localtime_r
nor localtime_s
are required to act as if tzset
has been
called. So if we want to detect any time zone changes, we need to call it explicitly.
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
This looks like a regression from bug 1361500.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Set release status flags based on info from the regressing bug 1361500
Updated•3 years ago
|
Updated•2 years ago
|
tim are there updates require for the patch? Looks like it has been reviewed yet ?
Pushed by andre.bargull@gmail.com: https://hg.mozilla.org/integration/autoland/rev/c9baea28c7fb Explicitly call tzset before localtime_r and localtime_s. r=tcampbell,bthrall
Comment 7•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Updated•2 years ago
|
Comment 8•2 years ago
|
||
Managed to reproduce the issue on an older version of Nightly from 2021-11-10 using Windows 10 x64.
Retested on Nightly 102 and Firefox 101.0b5 and the issue is not reproducing anymore.
Description
•