slangley@ 

Can you be more specific? Which part of webaudio is problematic? 
- WebAudio codes are pretty much standalone, and they are already in modules/webaudio.
- We don't have any IPC call except for the initial handshaking for audio device.

Hi hongchang@

I see what looks like audio related files in content/renderer/media, for example audio_message_filter.cc and friends.

Are these not part of WebAudio? If not, can you suggest what the right component would be?

Thanks.

slangley@

That would be the internal Media/Audio team. There is already on-going work on this:
https://docs.google.com/document/d/1s_Fd1WRDdpb5n6C2MSJjeC3fis6hULZwfKMeDd4K5tI/edit

I believe olka@ is the right owner.

Converstion of audio stream IPCs to Mojo is in progress:
https://docs.google.com/document/d/1awQoajq_DLmz2AIU9iweC0zEYlVuHCvEIRQepeYyxh8/edit?usp=sharing

We are not planning any further work in content/renderer/media in the near future though.

slangley@ - what rearrangements are expected there? The only context I found is 
https://docs.google.com/document/d/1hBKAYGGM2Zm7qhqXtdLSubklVDKUo9ir-vJtPEOx11Y/edit#heading=h.yc28az2hj3n0

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The STO team has pretty much done all of this, so =>olka to close.

(WebAudio isn't part of this, but media/audio is)