AudioContext latencies are values Chrome's audio stack can produce

Two AudioContext latencies are produced by the audio stack at particular moments, and their values are constrained in ways a constant is not. outputLatency is updated only when the context renders: until the first render callback it is exactly 0 (afterwards it is rounded to an 8 ms grid, or 1 ms once the page holds microphone permission). baseLatency is the buffer size divided by the sample rate, so baseLatency multiplied by sampleRate is a whole number of frames — 480 at 48 kHz, 441 at 44.1 kHz — and never less than the 128-frame render quantum.

The row checks three things: outputLatency is 0 on a context that has not rendered, baseLatency is a whole number of frames, and it is at least the render quantum. Every stock arm measured here followed all three, as audio_context.cc says it must. A JavaScript override that reports a realistic-looking outputLatency of 0.016 at construction fails the first: a context that has not rendered cannot know its output latency yet.

The failing side was written for the test rather than captured from a tool, so the row is information only. A context that never starts, for example one held suspended by the autoplay policy, keeps outputLatency at 0, which is the correct reading rather than a failure.