RFC: Should localizing time and relative words be separate concerns about relative-time-element HOT 8 CLOSED

👍 Having them together makes sense to me, since they're both basically friendlier translations of a UTC timestamp.

The only part that trips me up conceptually is that the update timer is always running, even if you only use the element to localize things. There's no practical issue — I just expect a thing that does localized time to run once and a thing that does relative time to run all the time. But having one line that surprises me seems better than having to work with two separate pieces for now.

from relative-time-element.

I just expect a thing that does localized time to run once and a thing that does relative time to run all the time

The timer should only touch from=now elements. However, I still need to make sure the timer isn't running if there are no elements on the page.

#7

from relative-time-element.

Oh, cool, didn't see #7.

from relative-time-element.

I just opened it!

from relative-time-element.

Trying to document and explain you can only use from or format is feeling weird to me. Maybe both these concerns can live in the same package but need to be separate elements.

from relative-time-element.

Maybe both these concerns can live in the same package but need to be separate elements.

Yeah, I guess having attributes that you can't use together feels a bit awkward. 👍 for two elements.

from relative-time-element.

One other option is to have just a single format attribute that accepts a strftime string or a keyword like now or relative.

from relative-time-element.

See #9.

from relative-time-element.