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

Fix for #241: Updating Timestamps #382

Closed
wants to merge 2 commits into from

Conversation

amenk
Copy link

@amenk amenk commented Oct 23, 2015

This commit fixes the problem, that timestamps are not refreshed.
Messages always stated "a few seconds ago", even time was passing.

  • Included jquery-timeago (patched version) and updates components.js
    (other dependencies where not updated)
  • Change template to HTML5 tag
  • Include the ISO timestamp
  • If a message is older then 24 hours, the full timestamp is displayed
    and no refreshing is initialized to save resources.
    Also I believe, that in this case the full timestamp is easier to conceive.

This commit fixes the problem, that timestamps are not refreshed.
Messages always stated "a few seconds ago", even time was passing.

* Included jquery-timeago (patched version) and updates components.js
  (other dependencies where not updated)
* Change template to HTML5 <time> tag
* Include the ISO timestamp
* If a message is older then 24 hours, the full timestamp is displayed
  and no refreshing is initialized to save resources.
  Also I believe, that in this case the full timestamp is easier to conceive.
@@ -77,7 +77,7 @@
<div class='attachments'></div>
<p class="content">{{ message }}</p>
<div class='meta'>
<span class='timestamp'>{{ timestamp }}</span>
<time datetime="{{ iso_timestamp }}">{{ timestamp }}</time>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

loss of .timestamp class breaks styling

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@amenk
Copy link
Author

amenk commented Nov 7, 2015

Fixed the class ... What do you think about the general approach? Unfortunately there are merge conflicts with the recent master ..
Tell me if I should take the time to resolve those.

@liliakai liliakai closed this Nov 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants