- From: Chris Lilley <chris@w3.org>
- Date: Thu, 1 Feb 2018 13:02:28 -0500
- To: public-web-security@w3.org
- Message-ID: <66612c33-b633-2f0e-2924-72115b53a6df@w3.org>
A gentle reminder about this review request. Web Audio API is on the agenda for the TAG f2f tomorrow; so we now hope to move to CR by the end of February. On 30-Nov-17 11:39, Chris Lilley wrote: > > Audio WG requests security review of the Web Audio API > > * Specification URL: https://webaudio.github.io/web-audio-api/ > * GitHub repo: https://github.com/WebAudio/web-audio-api > > The major change in the last year or two is the extensibility point. > We switched from ScriptProcessorNode > <https://webaudio.github.io/web-audio-api/#the-scriptprocessornode-interface-deprecated> > (running on the main thread, now deprecated) to Audio worklets > <https://webaudio.github.io/web-audio-api/#AudioWorklet> which are of > course derived from the TAG/CSS Houdini Worklet. Plus a lot of > detailed spec improvements and clarifications. Complete changes list > <https://github.com/WebAudio/web-audio-api/commits/gh-pages>. > > There is a Security and Privacy > <https://webaudio.github.io/web-audio-api/#Security-Privacy-Considerations> > self- assessment appendix. > > Ideally, we would like to move to CR by the end of 2017. Please let us > know if you would like more time to review. Review comments should > ideally be raised asissues on GitHub > <https://github.com/WebAudio/web-audio-api/milestone/1>. > > -- > Chris Lilley > @svgeesus > Technical Director @ W3C > W3C Strategy Team, Core Web Design > W3C Architecture & Technology Team, Core Web & Media -- Chris Lilley @svgeesus Technical Director @ W3C W3C Strategy Team, Core Web Design W3C Architecture & Technology Team, Core Web & Media
Received on Thursday, 1 February 2018 18:02:31 UTC