Actions
Bug #4667
closedTimeago losing its settings on refresh
Description
When Timeago updates its values it's losing its settings as it's not keeping a local copy and is using a global settings implementation. A new timeago usage is needed or current needs to be modified.
Updated by krileon about 10 years ago
Possible replacement if the moment settings can be changed on an instance by instance basis
- http://mattbradley.github.io/livestampjs/
Updated by krileon about 10 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Fixed in MR !420
Actions