On Tuesday, July 30, 2013 at 6:26 PM, Ehsan Akhgari wrote:
> We have been working on implementing the Web Audio API for quite a while
> now, and we've had an experimental implementation on Nightly and Aurora for
> several cycles now.
>
> We're getting close to a stage where we feel that we're ready to ship this
> API by default.
What led you to feel comfortable with shipping? Is it based on interoperability
with some significant content and another UA? Is there a test suite?
> There is still some implementation work to be finished,
> and there are a few spec issues to be resolved, but we're relatively
> confident that we can address all of these issues by the time we release
> Firefox 25, therefore I would like to announce the intent to ship this API.
Ship means no longer behind a flag, right?
> There is some risk involved from the spec level discussions which we're
> currently having in that the discussions may not finish in a timely
> manner. In that case, we will delay shipping this API until we reach a
> resolution on the W3C Audio Working Group, and I will follow-up to the list.
>
> Please let me know if you have any questions.
>
I'm admittedly a little bit concerned - if we ship, it's a strong signals to
the W3C Web Audio WG we are happy with the API that is spec'ed as is (that may
be true - it might be the best that the group can do and it might very well be
a spec from which interoperable implementations can be created). My personal
opinion about the spec is that it could be improved (lots of stuff seemed
underspecified, etc. when I tried to read it a few months ago - but maybe it's
better now) - if it mostly works across at least 2 browsers, then I guess it's
time to ship.
--
Marcos Caceres
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
