W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2011

Re: Adding Web Audio API Spec to W3C Repository

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Tue, 14 Jun 2011 20:59:29 +0300
Message-ID: <4DF7A181.3000309@helsinki.fi>
To: Ian Ni-Lewis <ilewis@google.com>
CC: Doug Schepers <schepers@w3.org>, Paul Bakaus <pbakaus@zynga.com>, "robert@ocallahan.org" <robert@ocallahan.org>, "public-audio@w3.org" <public-audio@w3.org>
On 06/14/2011 08:56 PM, Ian Ni-Lewis wrote:
> Multiple bugs have been filed in crbugs about the <audio> implementation
> in Chrome. This is a well-known issue.
>
> In my opinion there exists a strong will to fix the problems, but
> because the needs of audio programmers were not well known when the spec
> was implemented, a corrected implementation will require
> significant re-architecture.


Is that the case also with other implementations?
*Please* file bugs on all the implementations you have problems.


-Olli


> Ian
>
> On Tue, Jun 14, 2011 at 10:09 AM, Doug Schepers <schepers@w3.org
> <mailto:schepers@w3.org>> wrote:
>
>     Hi, Paul-
>
>     Olli Pettay wrote (on 6/14/11 11:01 AM):
>
>         On 06/14/2011 05:51 PM, Paul Bakaus wrote:
>
>
>             HTML5 Appcache offline caching sounds good, if this is
>             defining that
>             audio and video data is to be cached in an offline cache.
>
>             The HTML audio element would certainly be enough to meet our
>             current
>             demands. Implementations are broken, incomplete or perform
>             too bad. We
>             have yet to discover a single browser without audio issues.
>
>
>         I hope you have filed bugs about the issues you've seen.
>         That is the way to get problems fixed in implementations.
>
>
>     And a very pragmatic way to make sure that implementations are
>     reliable is to make sure that the test suite is adequate.  I suggest
>     that y'all:
>
>     1) look for any relevant tests in the existing HTML test suite
>     1a) review the tests to make sure they are correct
>
>     2) create and contribute tests for any missing behavior
>
>     3) file bugs with implementations, pointing to the spec and the tests
>
>     4) if you feel that the spec is missing something, or disagree with
>     the spec, propose changes to the spec
>
>
>     Regards-
>     -Doug Schepers
>     W3C Staff Contact, SVG, WebApps, Web Events, and Audio WGs
>
>
>
>
> --
> Ian Ni-Lewis
> Developer Advocate
> Google Game Developer Relations
>
Received on Tuesday, 14 June 2011 18:00:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:56 UTC