- From: Doug Schepers <schepers@w3.org>
- Date: Tue, 18 Jun 2013 00:15:19 -0400
- To: robert@ocallahan.org
- CC: Ehsan Akhgari <ehsan.akhgari@gmail.com>, Chris Wilson <cwilso@google.com>, Chris Rogers <crogers@google.com>, Chris Lowis <chris.lowis@bbc.co.uk>, Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>, "public-audio@w3.org" <public-audio@w3.org>, Alex Russell <slightlyoff@google.com>
Hi, Rob- On 6/17/13 11:09 PM, Robert O'Callahan wrote: > On Tue, Jun 18, 2013 at 2:05 PM, Ehsan Akhgari <ehsan.akhgari@gmail.com > <mailto:ehsan.akhgari@gmail.com>> wrote: > > I also believe that it's damaging to the Web for an engine to ship a > prefixed implementation of another engine, since doing that has the > potential of setting that into stone for an extended period of time, > once web developers realize that their content using > webkitAudioContext suddenly starts to work in Firefox without > modifications. > > If we require Web developers to make major modifications to work with > the unprefixed AudioContext, then for many of them it becomes easier to > just tell their users to use Chrome. Isn't this what script patches (like Chris' monkeypatch) –and script libraries in general– are for? I've always seen Mozilla as a browser vendor that is committed to making the Web better for users and for developers, and carrying over prefixes and alternate names is decidedly harmful, so I'm surprised to hear you take this position. What sort of education/evangelism efforts would convince you that this isn't necessary? What sites are using webkitAudioContext? Who has filed bugs or reports about lack of support in Firefox? Regards- -Doug
Received on Tuesday, 18 June 2013 04:15:28 UTC