On Tue, Jun 18, 2013 at 2:05 PM, Ehsan Akhgari <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. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w
Received on Tuesday, 18 June 2013 03:10:20 UTC