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
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
If moment-timezone is enabled, and set angularMomentConfig.timezone to some timezone, when the browser local timezone is not the same with angularMomentConfig.timezone, amTimeAgo will give different text on element's title and innerText (full date format).
I think it makes more sense to simply remove the .local() at the second location. We have the amLocal filter that the library users can utilize for this purpose.
Any chance you could send a pull request with this change?
If moment-timezone is enabled, and set angularMomentConfig.timezone to some timezone, when the browser local timezone is not the same with angularMomentConfig.timezone, amTimeAgo will give different text on element's title and innerText (full date format).
Problem is caused by the '.local()' here:
https://github.com/urish/angular-moment/blob/master/angular-moment.js#L233
https://github.com/urish/angular-moment/blob/master/angular-moment.js#L239
They should both use '.local()' or neither. May be it's better to give an 'alwaysLocalTimezone' option?
The text was updated successfully, but these errors were encountered: