WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #10660, comment 26


Ignore:
Timestamp:
09/02/2019 06:45:02 AM (5 months ago)
Author:
Rarst
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10660, comment 26

    initial v1  
    33Is the suggested endpoint dead? http://api.wordpress.org/core/ip-to-zoneinfo/1.0/?callback=abcd `({"errorcode":5,"errormessage":"GeoNames API could not be contacted"})`
    44
    5 Looked at `Intl.DateTimeFormat().resolvedOptions().timeZone` and browser support looks good by now (except IE), but there are reports that returned value is incorrect/inconsistent between browsers. Also the value might not at all be consistent with ''PHP'' time zone, which we need. I suppose we could do a very low hanging fruit implementation when suggestion is made if JS time zone matches exactly one of PHP time zones. Anything more comprehensive would require us to maintain complex multi-browsing mapping from possible JS values to PHP ones.
     5Looked at `Intl.DateTimeFormat().resolvedOptions().timeZone` and browser support looks good by now (except IE), but there are reports that returned value is incorrect/inconsistent between browsers. Also the value might not at all be consistent with ''PHP'' time zone, which we need. I suppose we could do a very low hanging fruit implementation when suggestion is made if JS time zone matches exactly one of PHP time zones. Anything more comprehensive would require us to maintain complex multi-browser mapping from possible JS values to PHP ones.