Ogg formats in HTML5: Difference between revisions

Revision as of 23:04, 30 December 2014

Revision as of 17:03, 5 May 2015

Line 18:

** The HTML5-conformant player, not having to be coded for compatibility with different browsers, could make bugs and exploits easier to find during browser development, and any exploits found would only be able to target that one browser.{{clarifyme|date=January 2012}}

* [[Free software]] encoders would compete with rival proprietary encoders, increasing encoder quality through competition.{{fact|date=January 2012}}

* Embedding of multimedia by the use of clear and straightforward <code>video</code> and <code>audio</code> elements would require less effort than mastering the [[HTML element#Images_and_objectsImages and objects|<code>object</code>]] element or learning [[ActionScript]] as required by Adobe Flash.{{fact|date=January 2012}}

[[Chief technical officer|CTO]] at [[Opera Software]], [[Håkon Wium Lie]] explained in a [[AtGoogleTalks|Google tech talk]] entitled "The <video> element" the proposal of Theora as the video format for HTML5:<ref>{{cite web |title=Håkon Wium Lie on the video element in HTML 5 |url=http://video.google.com/videoplay?docid=5545573096553082541&ei=LV6hSaz0JpbA2AKh4OyPDg&hl=un |accessdate=2009-02-22 |publisher=Google Video |date=2007-03-29}}</ref>