UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36

Steps to reproduce the problem:
1. Travel to Sydney, Australia
2. Connect to internet
3. From the billion of example websites to choose from, here is a couple that show AEST instead of AEDT timezone: 
http://www.clocktab.com/
https://messages.android.com/

What is the expected behavior?
It's currently 11:34 AM. The time shown on the websites is 10:34 AM. Or in some instances the relative time (eg "10 minutes ago") indicates that it is being calculated from 10:34 AM.

What went wrong?
Chrome 71 "Stable" went wrong. Websites are either using the JavaScript Date object or they are using libraries that are just wrappers to the Date object.

Did this work before? Yes Chrome 70

Chrome version: 71.0.3578.80  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

This has been reported in other Issues. How do we get your attention? Hopefully this will.
 

Deleted: Chrome71_Regression_DateObject.png 1.1 MB

	Chrome71_Regression_DateObject.png 1.1 MB View Download