Clock

Documentation Index

Fetch the complete documentation index at: https://docs.cognite.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Clock

​

When to use

• Time-only input where a visual selector is clearer than free text.
• Paired with Calendar when both date and time are required.

​

When not to use

• When only a date is needed, use a Calendar instead.

• Do match the clock format (12hr/24hr) to the user’s locale or application setting — don’t hardcode one.
• Do include AM/PM selection clearly when using 12-hour format; ambiguity here causes real errors.
• Don’t include seconds unless the context requires it (log timestamps, precise scheduling) — it adds complexity most users don’t need.
• Don’t use Clock for time range input — pair two instances with clear “start” and “end” labels, or use a dedicated range primitive.

​

Behavior

• When paired with Calendar, the date and time should feel like one composed input — changes to either should update a single combined value, not two separate ones.
• If the time value has constraints (e.g. only future times, business hours only), disable invalid times rather than letting users select them and fail on submit.

​

Often used with

• Calendar when both date and time are required and DateTimePicker.