👋 Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

• 🎨If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
• ⏩If this is a PR that includes changes to an interaction, please include avideo recording in the description.
• ⚠️If this is urgent, please visit us in#primer on Slack and tag the first responders listed in the channel topic.

I'd love for@keithamus to approve this as he is working on it. Fine from primer FR side

Thanks, I'm looking into fixing this but I have higher priorities for now. A fix will come though!

Sorry for the delay on my end, adding this to the first responder board to pick up 👀@keithamus just wanted to check-in, what are the next steps for this?

I looked into this today and have become thoroughly confused. Are you specifying anyprecision argument anywhere?

If I try copy/pasting your test cases into example/index.html, it always gives me something like "1 year, 6 days, 4 minutes, 24 seconds." I don't understand why the tests fail the way they do when noprecision is specified.

@camertron according to the README the precision defaults tosecond, so I'd assume that's how it works. I don't think it changes anything in this context, though.

I just put this into an HTML (using v4.4.4 via npm):

<relative-timeformat="duration"datetime="1944-12-13"></relative-time>

It showed "81 years, 2 months, 22 hours, 21 minutes, 45 seconds" for me. Even if I set the precision as high asyear, then that would still be wrong—it should be 80 years. In other words, given a long enough duration, all precision levels are affected.