I have a similar issue where Chrome doesn't reflect the local system timezone when fetching it with Date() - Version 67.0.3396.99

Able to reproduce the issue on Windows 10, mac 10.13.3 and Ubuntu 17.10 using chrome reported version #67.0.3396.99 and latest canary #70.0.3503.0.

Bisect Information:
=====================
Good build: 67.0.3389.0
Bad Build : 67.0.3390.0

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/f42b19bde0ce6e2d52fadc34a19b005dc236c2b8..7bed949c66408be72fa74397b34ddb0835b12df9

V-8 Autoroll change log:
https://chromium.googlesource.com/v8/v8/+log/77df816c..7e9556c8

From the above change log suspecting below change
Reviewed-on: https://chromium-review.googlesource.com/572148

jshin@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks...!!

Back then, Asia/Tokyo was GMT+0918. 

BTW, why do you care about that old time?  

See https://en.wikipedia.org/wiki/Japan_Standard_Time

I'm not critically depending on old times or anything. In the course of testing out the edges of date parsing I noticed this strange behavior which isn't in line with other modern engines so I thought I'd report it. It may represent an underlying bug that may affect others (I don't know how far back it starts).

Of course there were no timezones back then so the reporting of the timezone shouldn't be expected, however this runs a bit deeper than that as the actual minutes are incorrect, so it seems worth looking into.