Re: Sites using webkitAudioContext only

It's true that Rovio marketed this as a Chrome app when it was written (I
think at the time, only Chrome supported some of the APIs they used).  But
I wouldn't want us to do something kludgy like URL-switching behavior, and
in the LONG term I don't even want Chrome to support webkitAudioContext; I
would want us to get them to update their app, so they could use the same
unprefixed, proper-standards-code API across the board (and then could be
enabled across browsers).  We're not going to flip that switch all at once,
but it is certainly my goal.

Jer, very pleased at your response.  Where are you standing on prefixed vs.
unprefixed AudioContext support?  (Just trying to think through an
evangelism plan for once iOS7 ships.)

On Thu, Jun 13, 2013 at 2:07 AM, Chris Lowis <> wrote:

> Chris Wilson writes:
> > Chris is absolutely correct that there are some critical apps out there
> today
> > that use the API as it is.  I would not, for example, like to be the one
> who
> > breaks the sound in Angry Birds
> I don't want to go to far off-topic, but Angry Birds is specifically
> marketed as a Chrome application in their URL
> ( Couldn't Chrome continue to support the
> interfaces that Rovio have coded to if you were worried about breaking
> the sound in that game, while still allowing us to make changes to the
> spec?
> Cheers,
> Chris
> -----------------------------
> This e-mail (and any attachments) is confidential and
> may contain personal views which are not the views of the BBC unless
> specifically stated.
> If you have received it in
> error, please delete it from your system.
> Do not use, copy or disclose the
> information in any way nor act in reliance on it and notify the sender
> immediately.
> Please note that the BBC monitors e-mails
> sent or received.
> Further communication will signify your consent to
> this.
> -----------------------------

Received on Friday, 14 June 2013 17:40:18 UTC