Context Navigation

Changes between Initial Version and Version 1 of Ticket #4480, comment 15

-                      initial
+                      v1
 Not sure about names for the new fields, if they will hold timestamps they might be better named as such? Seems confusing that `date` field is a string, but `date_utc` is a timestamp. `timestamp` and `timestamp_end` maybe?
+`strotime()` for reversing timestamps is flawed and we are removing it in core. Is there now better time zone information than seconds offset to use?
+For more robust example [https://github.com/WordPress/wordpress-develop/blob/c20372e0aa6d82fb4fdd65ed921d843b7fff6177/src/wp-includes/functions.php#L184-L191 see `date_i18n()`] (except time zone would be event, not site in this case).
+`strotime()` for reversing timestamps is flawed. Is there now better time zone information than seconds offset to use?
 Also I still would like to see API response contain event time zone somewhere, if it's now available? That's just meaningful to have, even if core won't use it right now.
+Gave wrong direction conversion example, not awake yet, edited out. :)