W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: MediaElementAudioSourceNode and cross-origin media resources

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 24 Jul 2013 09:28:54 +1200
Message-ID: <CAOp6jLbmkOEy5he9pCQOKKRZ5b1v1EQHr0SzKfMOQdFfLbOutw@mail.gmail.com>
To: Joseph Berkovitz <joe@noteflight.com>
Cc: Ehsan Akhgari <ehsan.akhgari@gmail.com>, "public-audio@w3.org" <public-audio@w3.org>
On Wed, Jul 24, 2013 at 8:09 AM, Joseph Berkovitz <joe@noteflight.com>wrote:

> Not only should we subject this to CORS rules, I think we *must* subject
> it to CORS rules. Audio assets are commonly delivered from CDNs and these
> are typically located at an origin foreign to the containing page.

Sure. However, authors will have to use the crossorigin attribute on the
media element to generate a CORS-enabled request.

> I note that AudioBuffer.decodeAudioData obeys CORS as a fact on the ground
> in both the FF implementation and Webkit/Blink.

I don't see how CORS is relevant to decodeAudioData. decodeAudioData takes
an ArrayBuffer, which can never be cross-origin.

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, 23 July 2013 21:29:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:23 UTC