On Mon, Nov 10, 2008 at 6:50 PM, Robert O'Callahan <[EMAIL PROTECTED]>wrote:
> Should <video> and <audio> elements be able to load and play resources from > other origins? How would this affect the very common scenario where content sites put static and large data under a separate domain. This is commonly done to avoid sending Cookies and other headers, while also decreasing load times, as the content is now being loaded from a different domain. For example: What are my limitations, if I put my video at http://ex.cdn/, but load it from http://www.example.com/ ? Is there a way for me to whitelist a particular list of hosts/domains? Would progress bars, loading different clips, captions, etc. be restricted? What happens if there is metadata in the media file container that is example.comspecific, is there a way to get access to it? -- Sander
