Re: [webkit-dev] Request for position on AudioContext.outputLatency

gt;> >>> Cheers, >>> Hongchan >>> >>> >>> On Mon, Dec 13, 2021 at 1:15 AM youenn fablet wrote: >>> >>>> Looking at >>>> https://www.w3.org/TR/webaudio/#dom-audiocontext-outputlatency, it >>>> states that:

Re: [webkit-dev] Request for position on AudioContext.outputLatency

ng 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.

[webkit-dev] Request for position on AudioContext.outputLatency

(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

Re: [webkit-dev] Request for position: Aligning high-resolution timer granularity to cross-origin isolated capability

-Spectre timing attacks? > Could you elaborate on those 2 points? > > Thanks, > Geoff > > On Mar 17, 2021, at 3:38 AM, Yoav Weiss via webkit-dev < > webkit-dev@lists.webkit.org> wrote: > > Hey folks, > > We recently changed <https://github.com/w3c/hr-time/p

[webkit-dev] Request for position: Aligning high-resolution timer granularity to cross-origin isolated capability

Hey folks, We recently changed the HR-time spec to better align its resolution clamping with cross-origin isolated capability