Updates:
Summary: timezone offset and timezone string may become inconsistent if
timezone changes in d8
Labels: -Priority-Medium Priority-Low
Comment #5 on issue 2861 by [email protected]: timezone offset and timezone
string may become inconsistent if timezone changes in d8
https://code.google.com/p/v8/issues/detail?id=2861
It is unfortunate that issue tracker doesn't show that chromium issue
406382 was merged into this issue. These are actually two separate issues.
This issue concerns only d8 shell. We don't have hooks in d8 that check for
system timezone change and call
v8::Date::DateTimeConfigurationChangeNotification. I am considering adding
this code to d8 as low priority.
V8 embedders should notify V8 on timezone change as Mark mentioned in
comment #1. All internal date caches in V8 are cleared on
v8::Date::DateTimeConfigurationChangeNotification.
Five months ago Mark landed https://codereview.chromium.org/251613002 which
sends timezone change notification to V8 on all platforms including
ChromeOS. Maybe crbug.com/406382 is caused by a regression since then?
I am unmerging crbug.com/406382 from this issue.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
