Looking at https://www.w3.org/TR/webaudio/#dom-audiocontext-outputlatency, it states that: > If the audio output device is changed the outputLatency <https://www.w3.org/TR/webaudio/#dom-audiocontext-outputlatency> attribute value will be updated accordingly.
The use case seems ok, but I worry about fingerprinting if it means this allows a web page to passively identify user speakers. Say I switch from builtin speakers to Bluetooth headset using MacOS system menu. If so, the spec should identify this as potential fingerprinting and should provide mitigations. And we should evaluate fingerprinting-free alternatives. What does PING WG think about this? Le lun. 13 déc. 2021 à 09:39, Yoav Weiss via webkit-dev < webkit-dev@lists.webkit.org> a écrit : > (Sent on behalf of Hongchan Choi, who failed to subscribe to this mailing > list) > > Hey folks! > > AudioContext.outputLatency is to inform the time at which the first sample > in the buffer is actually processed by the audio output device. This is > useful when synchronizing the audio generated by Web Audio to other audio > or video sources or to visual cues [1]. > > This is already implemented in FireFox and we're looking to ship it in > Chrome soon [2][3]. Would you all be interested in this feature? > > Thanks, > Hongchan > > [1] https://www.w3.org/TR/webaudio/#dom-audiocontext-outputlatency > [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1324552 > [3] > https://groups.google.com/a/chromium.org/g/blink-dev/c/dTQniJNVVMY/m/hPFwY1fbBQAJ > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev