Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: the "created on" date associated with my dev.to comment is incorrect #11643

Closed
jorroll opened this issue Nov 27, 2020 · 3 comments
Closed

Comments

@jorroll
Copy link

jorroll commented Nov 27, 2020

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):

  • OS, version: Chrome OS
  • Browser, version: Google Chrome, 86
@github-actions
Copy link
Contributor

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.

@jorroll
Copy link
Author

jorroll commented Nov 28, 2020

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.

@rhymes
Copy link
Contributor

rhymes commented Nov 28, 2020

Hi @thefliik thanks a lot for the info, this is a known bug, can you add your findings to the discussion in #7561 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants