Re: New browser engines - what does that mean for our work on web audio / web midi

On Thu, Apr 4, 2013 at 6:38 AM, Ehsan Akhgari <>wrote:

> Servo is a research browser engine which currently supports just enough of
> web specs to render the most basic pages.  To the best of my knowledge
> there is currently no audio support in Servo so it currently will not
> affect our efforts here much.
> Blink is a fork of WebKit so I assume is going to inherit the current
> WebKit's Web Audio implementation, but given that Google will no longer
> contribute directly to WebKit, it means that further changes to the spec
> should now be implemented by three different browser engines as opposed to
> two, which is great news as far as I'm concerned, as that helps us find
> implementation issues faster.

I just wanted to say that I *do* hope to continue working in the Web Audio
code in WebKit as well as Blink.

> On the question of prefixes it seems like Blink is not going to drop any
> of the existing prefixes so for Web Audio it doesn't seem like anything
> would change.  For Web MIDI, it seems like Blink will not ship a prefixed
> implementation before it matches their new features criteria, which again
> is great news in that we will hopefully be able to avoid a lot of the
> current problems caused by WebKit shipping a prefixed implementation.
> Cheers,
> --
> Ehsan
> <>
> On Thu, Apr 4, 2013 at 7:47 AM, Olivier Thereaux <
>> wrote:
>> Hi all,
>> The past two days have been rich in announcements, notably the unveiling
>> of work on both the Servo [1][2] and Blink [3] browser engines.
>> [1]
>> [2]
>> [3]
>> Is it too early to ask out loud what implications these will have on our
>> work? I am assuming that it will mean that we will go from having two
>> distinct implementations (modulo a few different ports) to having (at
>> least) three.
>> Things I am wondering:
>> * How does this affect our current discussion on vendor prefixes?
>> * How does this affect the development of the webkit implementation of
>> web audio and web midi?
>> * How does this affect the current development of web audio on gecko?
>> I understand this is a public mailing-list where some things can't be
>> shared yet, and of course not all questions have answers yet. But it would
>> be interesting to hear what members of the group can share of their
>> understanding of the situation.
>> Thanks,
>> --
>> Olivier
>> -----------------------------
>> This e-mail (and any attachments) is confidential and
>> may contain personal views which are not the views of the BBC unless
>> specifically stated.
>> If you have received it in
>> error, please delete it from your system.
>> Do not use, copy or disclose the
>> information in any way nor act in reliance on it and notify the sender
>> immediately.
>> Please note that the BBC monitors e-mails
>> sent or received.
>> Further communication will signify your consent to
>> this.
>> -----------------------------

Received on Thursday, 4 April 2013 17:31:33 UTC