Times don’t render properly for me; discourse seems to think my time zone is utc.
I’ve had issues with getting the date/time formatting right (perhaps from manually editing the markup, which seems easier to break than I’d hope, and I don’t fully get the exact correct markup structure). I redid that thread. See if it works now.
Still bugged on my computer. Works fine on Android.
Weird. Sounds like Discourse isn’t recognizing your time-zone correctly. Try a test at meta discourse (like report the bug and post a date/time within the report post as a test)?
Also works fine on chromium and epiphany. Seems to be a Discourse+Firefox bug (it also happens on Windows and on Fedora with a clean profile).
Can confirm this, also on Firefox. Works fine on Eolie.
UPDATE: you using a screenshot was confusing me, I just saw the bug in your screen shot! I’m still not experiencing it.
Maybe one of you who see the bug can reply on that thread
@wolftune: thanks. Here are a few details if it helps.
Affected browser/OS: Firefox 63/Arch Linux
Post content: date tag (e.g. smichel’s screenshot) and post timestamps (the one shown when the cursor is hovered over the relative time)
$ date Sat Nov 17 14:42:59 EST 2018 $ date -u Sat Nov 17 19:43:01 UTC 2018 $ timedatectl | grep zone Time zone: EST5EDT (EST, -0500)
JS console output:
Intl.DateTimeFormat().resolvedOptions().timeZone "UTC" moment.tz.guess() "Etc/UTC"
I relaunched Firefox without a config, letting it create a new one at ~/.mozilla and the local time shows correctly for me. Haven’t yet found the source causing the js library to guess the wrong timezone.
Intl.DateTimeFormat().resolvedOptions().timeZone "EST5EDT" moment.tz.guess() "EST5EDT"
Looks like this might be related to enabling
Good find, thanks!
I thought it might be related to a privacy setting, but it wasn’t tracking protection. Completely forgot about resist fingerprinting, confirmed toggling this changed the timezone display.
In Discourse, the date tag allows adding timezones to show on cursor hovering over the date tag display. At least for meeting time display it may help a bit if the most common timezones (e.g. tz of active volunteers) are listed.
[Meta comment: I marked your post as the solution, but should have left it for you as OP to do so, hence removed it again.]