bypassing chrome intl timezone bug fix #517

[bolasblack]

No description provided.

[jsf-clabot]

All committers have signed the CLA.

[mattjohnsonpint]

Thanks, but I don't think this much examination is required. The reported bad results have all been three-character abbreviations, from what I have been able to ascertain. Closing in favor of #553

[bolasblack]

Hi @mj1856 , I think you misunderstood me, I was trying to fix the issue #517 , not #423

In some region (for example Asia/Shanghai), when I executing Intl.DateTimeFormat().resolvedOptions().timeZone in chrome 61.0.3163.100, I will get America/Chicago, not Asia/Shanghai

I think check Intl.DateTimeFormat().resolvedOptions().timeZone.length > 3 can not fix this issue.

[mattjohnsonpint]

Oh, I see. Let me take another look at this. Thanks.

[gregclarke]

In addition to the above, in some circumstances the resolved timezone is incorrect. On arch linux firefox version 56.0.2 Intl.DateTimeFormat().resolvedOptions().timeZone returns Etc/GMT-10 which is an hour out due to daylight savings (correct timezone is Australia/Sydney). The length check doesn't work in this case either. I've temporarily solved by using
var tmpName = intlName.split('/')[0]; if (intlName && tmpName.length > 3)

[iffy]

@mj1856 Can you please reopen this/reconsider this as a way to fix 517?

[morajabi]

@mj1856 I have this problem :( How can we fix it?