- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 21 Mar 2019 09:59:08 -0700
- To: Hongchan Choi <hongchan@google.com>
- Cc: Paul Adenot <padenot@mozilla.com>, John Peter Blanco <John.Blanco@colorado.edu>, "public-audio@w3.org" <public-audio@w3.org>
- Message-ID: <CAE3TgXES+-Z4Kh_PT8G6Zc+GR1zMHrT2+ba-pvvjCNQexuLr2g@mail.gmail.com>
In addition, if you have some small examples, feel free to file issues at crbug.com/new. I'll look at them and file spec/browser issues as needed. (Be sure to set the component to Blink->WebAudio if you can.) On Thu, Mar 21, 2019, 8:57 AM Hongchan Choi <hongchan@google.com> wrote: > In order to have more visibility on it, I created a tracking issue for > this: > https://github.com/WebAudio/web-audio-api/issues/1842 > > John, thanks for your feedback and please feel free to follow up on the > link above. Your report will greatly help us assess the problem quickly. > > Best, > Hongchan > > > On Thu, Mar 21, 2019 at 2:56 AM Paul Adenot <padenot@mozilla.com> wrote: > >> John, >> >> If you could write a short document outlining the various problems you're >> seeing, one of us could quickly assess the situation, and determine whether >> a particular implementation is not respecting the spec (and in fact, no >> implementation fully implement every little detail of the spec right now), >> or if the spec is simply unclear about something. It could be (and has >> historically been) both reasons, so without looking into the particular >> problem, it's hard to tell. Out of this, we'll probably end up writing Web >> Platform Tests (which are tests being run on all implementations), to make >> it easy to determine which implementation is (are) correct and which is >> (are) wrong. >> >> Then, we'll go and fix either the spec, the implementations, or both, >> after having filed issues in the relevant issue trackers. >> >> Thanks for contacting us, hopefully we can sort this out and come out of >> this with a better spec and better implementations. >> Paul. >> >> On Wed, Mar 20, 2019 at 10:10 PM John Peter Blanco < >> John.Blanco@colorado.edu> wrote: >> >>> Greetings, >>> >>> >>> >>> I work for an organization that develops interactive educational >>> web-based simulations (see https://phet.colorado.edu for more info). >>> We are currently adding sound to many of our simulations, and I’m running >>> into issues due to inconsistencies in the implementation of Web Audio >>> across the leading browsers. I already reported one bug to Mozilla, which >>> they have agreed to resolve, but some of the other problems that I’m >>> finding are a little less clear as to which browser is incorrect, or if the >>> spec is just vague on some points. I was wondering if there was someone >>> there that I could work with to help sort some of this out. I’m happy to >>> provide code that demonstrates the differences in order to minimize the >>> level of effort on your end, and I’m also happy to report the issues to >>> Chrome/Mozilla/Apple/Microsoft once I’m clear on which browsers are in >>> violation of the spec. >>> >>> >>> >>> Thanks and Best Regards, >>> >>> >>> >>> John Blanco >>> >>> PhET Interactive Simulations >>> >>> University of Colorado, Boulder >>> >>> >>> >>
Received on Thursday, 21 March 2019 16:59:43 UTC