I4.04.3exact time on demanddesign

Exact time should remain available on hover or in detail

Aliases: timestamp tooltip · precise instant · progressive time · copyable datetime

What it is

Using a relative label on a list to scan recency does not mean the exact instant is allowed to vanish. Exact time should be available on hover or in detail: the default view may be coarse, but when someone needs to cite, verify, or forward this row, the full instant must be reachable in one or two actions. This is not printing both formats on every row. It is putting the full instant on a discoverable next layer.

Why it happens

Writing the full instant on every row on a screen slows recency judgements, raises visual density, and washes out what relative labels were for. Giving no full instant at all leaves relative holding a job it cannot do: citation. Layering splits the two tasks: the default layer serves scanning, the on-demand layer serves checking. Hover, long-press, opening detail are signals of “I need to check now”; expanding the full instant on those signals charges the cost only to the people who are actually checking.

“Available” also means copyable, speakable, and stable. A tooltip that flashes on hover and cannot be selected is, for someone pasting a time into a ticket, the same as nothing. Touch has no hover; long-press or entering detail must reach the same layer, or the exact instant exists only for pointer users.

Where it stops holding

Surfaces that are verification by nature (a log, a ledger, a clinical timeline) should default to the exact instant, not hide it. On touch, hover-only exact time is the same as not shipping it. Screen-reader users cannot reach a pointer hover; the full instant needs to live in focusable detail or in the accessible name of the cell — without turning every row’s accessible name into a long date string, which makes scanning unusable. If a relative label has already refreshed into a wrong “just now”, the next layer’s exact instant must still be right: the on-demand layer corrects the full coordinate; it must not inherit a stale distance phrase.

Applying it

  • Default rows use relative or a short form. Hover, long-press or detail offers the full local instant, and it can be copied.
  • Touch and pointer must reach the same full instant. Do not ship hover only.
  • For screen readers, put the full instant in detail or in an optional hint; do not force a long date on every row during list scanning.
  • How to check: on a “three minutes ago” row, without leaving the list, get the full instant via hover or long-press and copy it. Repeat with fingers only, mouse off. Open detail; the full instant should match the on-demand layer. An on-demand layer made of unselectable flash text should fail the copy task.

Related

  • Same group: I4.04.1 Relative time fits the recent past; absolute time fits reconstruction · I4.04.2 Relative timestamps go stale unless they are refreshed
  • Nearby: S2.01 Date and Time Formats · I4.05 Time zones
  • Search terms: exact timestamp · time on hover · progressive disclosure time

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/I4.04.3