- From: Chris Rogers <crogers@google.com>
- Date: Wed, 9 May 2012 15:55:19 -0700
- To: robert@ocallahan.org
- Cc: Jer Noble <jer.noble@apple.com>, "public-audio@w3.org" <public-audio@w3.org>
Received on Wednesday, 9 May 2012 22:55:49 UTC
On Wed, May 9, 2012 at 3:32 PM, Robert O'Callahan <robert@ocallahan.org>wrote: > I think it would be simpler for authors if everything "just worked" as far > as possible. With the proposed renderState and onrenderstatechange, some > developers are likely to simply forget to handle it --- if the renderState > is never idle on their platform or they simply don't test that case --- and > their apps will be broken. > > So how about adding no new APIs, but instead just automatically pause the > entire audio graph while the page does not have access to the audio > hardware? > I could be wrong, but I think Jer is saying that the graph *would* be automatically paused. It's the restarting/resuming that Jer would like authors to have the opportunity to control instead of it automatically starting to play the instant the phone call ends. Chris > > Rob > -- > “You have heard that it was said, ‘Love your neighbor and hate your > enemy.’ But I tell you, love your enemies and pray for those who persecute > you, that you may be children of your Father in heaven. ... If you love > those who love you, what reward will you get? Are not even the tax > collectors doing that? And if you greet only your own people, what are you > doing more than others?" [Matthew 5:43-47] > >
Received on Wednesday, 9 May 2012 22:55:49 UTC