Open julianlam opened 1 year ago
Solution 2 works fine (<noscript>
tag inside of timeago span/a), as the content inside of it gets removed when timeago is rendered.
The only consideration then is that the ISO time string is not actually all that user-friendly, so we'd need to send in a locale string alongside the ISO timestamp.
Subjective, I know, but could we expect GNU LibreJS and/or NoScript users to actually prefer ISO timestamps instead of locale-specific strings that may or may not be a bit of a mess depending on how well your operating system + browser combination actually handles that locale detection? I personally haven't been able to get English/Denmark nor English/Canada to work reliably, so I still see things like "PM" every now and then if there's no freely customizable user-configuration available
An ISO date while readable for humans, is not meant to be a format digested by humans, but rather a machine... At least this is my understanding.
The assumption here is that a user will have proper local settings so that the local string will be rendered in the correct user preferred format.
If that isn't the case, then the fix would be an adjustment to the OS settings, which I would hope is doable.
We currently render relative timestamps via the timeago plugin. Users without javascript enabled don't see them, for obvious reasons.
Solutions
<noscript>
tag next to it.