You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I posted this comment on dev.to around 11:30pm, 11/26/20 in California. I'm viewing the comment in the same location I posted the comment, and the "created on" date for the comment shows November 27th (it should show Nov 26th). I suspect a DST issue is the cause.
Thanks for the issue! We'll take your request into consideration and follow up if we decide to tackle this issue.
To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.
To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss and we will follow up within 3 business days.
For full info on how to contribute, please check out our contributors guide.
Of note: the <time> element wrapping my comment's created on date has a title attribute the contains the correct created at time. It's just the text date that the <time> element is wrapping that is incorrect--further reinforcing my suspicion that this is a server DST issue.
Describe the bug
I posted this comment on dev.to around 11:30pm, 11/26/20 in California. I'm viewing the comment in the same location I posted the comment, and the "created on" date for the comment shows November 27th (it should show Nov 26th). I suspect a DST issue is the cause.
To Reproduce
You can see the problematic comment here: https://dev.to/johncarroll/comment/18dp8
Expected behavior
The date associated with my comment should be Nov 26th.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: