Dates on events now work across timezone boundaries.
So if you are in Portland and create an event for 11pm, and then access the site from London, it will show correctly as being at 6am, and if edited from France and then you fly back to Portland, the time will show 11pm there as expected.
Basically... we store UTC, and we return HTML containing UTC, but the display and forms use JavaScript to take the local browser setting, so that it always show the time according to whatever your browser locale is.
Proposal:
When editing, if a location is chosen, treat the time input as location-local. Ignore browser locale.
When displaying, if the location is in the same timezone as browser locale, show local time, otherwise show both location-zoned time and browser-locale-zoned time.
Dates on events now work across timezone boundaries.
So if you are in Portland and create an event for 11pm, and then access the site from London, it will show correctly as being at 6am, and if edited from France and then you fly back to Portland, the time will show 11pm there as expected.
Basically... we store UTC, and we return HTML containing UTC, but the display and forms use JavaScript to take the local browser setting, so that it always show the time according to whatever your browser locale is.