outputLatency normative, non-optional

[svgeesus]

Describe the issue

outputLatency is a required part of the spec.

Where Is It

https://webaudio.github.io/web-audio-api/#dom-audiocontext-outputlatency

Additional Information

We don't have two implementations. The Chrome bug indicates a lack of urgency to add this.

Given that, I was asked on today's transition call why is is not optional, or non-normative. Is it not implemented because of fingerprinting risk (even if quantized) or because of difficulty in estimating the latency?

[rtoy]

That's a good question. Unless we can resolve that here in this issue, we might have to wait for the teleconf next week to decide on what to do.

But there is probably a fingerprinting risk.

I also think estimating the latency is difficult and sometimes devices lie. I defer to @padenot about that since Mozilla has implemented this.

[svgeesus]

To be clear, this one isn't a blocker on publishing a Proposed Rec; the transition was approved today.

The fingerprinting risk is already mentioned in the spec.

[rtoy]

Teleconf: outputLatency is very important for synchronizing audio and video together. MediaElement does this automatically, so the appropriate code is in each browser.

So, there's no change needed here. This is required.

[rtoy]

Closing. This is not an optional part of the spec. It is a bug in Chrome (and Safari?) that it is not yet implemented.