Can't activate timeago on elements prior to inserting them into the DOM

[jhass]

Opening issue since no reaction to #190 (comment)

[rmm5t]

Yes, this is true, and an unfortunate limitation of Timeago. I've had long-time plans to write Timeago 2 to help solve these issues, but time keeps escaping me. I'm also hesitant to pull-in related PRs, because of the rewrite that's still in my head.

For now, you need to call timeago() on new elements after they've been inserted into the DOM.

However, if an element is removed from the DOM, timeago automatically handles this and disposes of it on the next cycle.

[kevin-brown]

Just pointing out that this was made in b5a364d, so downgrading to 1.4.0 does fix the issue.

We were recently hit by this issue when we decided to upgrade timeago.

[rmm5t]

@kevin-brown Thanks for the extra info. That helps me understand the underlying issue better.

b5a364d had some importance, so if there are any ideas about how to keep that working but also improve the scenario reported here, I'm open to reviewing a PR.