Identify the clock behind each value
MDN distinguishes mediaTime from presentation-related timestamps. Media time locates the frame on the programme timeline, while browser timestamps describe processing or composition events. Comparing values from different clock systems without a mapping produces a number with no clear meaning.
For an illustrative overlay, a developer might align an annotation to a known media-time interval. That task does not require claiming when the real-world camera captured the scene. An absolute live-delay measurement would need an appropriate origin reference and an end-to-end method beyond the callback alone.
Counters are observations, not diagnoses
The documented presentedFrames count can help detect whether callback observations missed frame submissions. A gap between callback counts is not automatically the number of corrupted network packets or proof that the source broadcaster omitted those pictures. Keep the unit as submitted frames.
Suppose two observations report counts 100 and 103. The difference is three submissions between the reported states. To explain why callbacks or displayed motion behaved as observed, a developer still needs scheduling, decoding and application context. Avoid turning that simple difference into a causal claim about the broadband connection.
Describe instrumentation honestly
Record browser version, callback metadata, selected media and the purpose of the measurement. A debugging overlay can affect the application workload, so a result from an instrumented page should retain that condition. It is not automatically identical to an uninstrumented viewer session.
If the viewer reports judder, combine frame-related observations with what was actually seen and whether media delivery remained healthy. Do not replace a display-cadence investigation with one counter, or claim a hardware benchmark from documentation alone. This reference describes a possible technical method; it does not assert that IPTV Australia measured the user's device, source or physical panel.
Questions about this guide
Is mediaTime an absolute camera capture time?
No. It identifies a position on the media timeline.
Does a callback-count gap prove a network fault?
No. It needs browser, scheduling and playback context.