HTML video: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Undid revision 569253792 by 92.27.156.6 (talk): non-neutral to the other side, please find sources to cite so that it can't be just edited to say the opposite
Line 2: Line 2:
The '''[[HTML5]]''' draft specification introduced the '''video element''' for the purpose of playing videos or movies,<ref name = "spec">{{Cite web| url= http://www.w3.org/TR/html5/video.html#video| title= The video element| work= HTML5: A vocabulary and associated APIs for HTML and XHTML|publisher=[[World Wide Web Consortium]]|date=24 June 2010|accessdate=2010-09-27 | quote =A video element is used for playing videos or movies.}}</ref> partially replacing the [[object element]]. HTML5 video is intended by its creators to become the new standard way to show video on the web without plugins, but has been hampered by lack of agreement as to which [[video format]]s should be supported in web browsers.
The '''[[HTML5]]''' draft specification introduced the '''video element''' for the purpose of playing videos or movies,<ref name = "spec">{{Cite web| url= http://www.w3.org/TR/html5/video.html#video| title= The video element| work= HTML5: A vocabulary and associated APIs for HTML and XHTML|publisher=[[World Wide Web Consortium]]|date=24 June 2010|accessdate=2010-09-27 | quote =A video element is used for playing videos or movies.}}</ref> partially replacing the [[object element]]. HTML5 video is intended by its creators to become the new standard way to show video on the web without plugins, but has been hampered by lack of agreement as to which [[video format]]s should be supported in web browsers.


http://gigisanchezonline.webs.com/bibliography<video controls="controls" autoplay="autoplay">
==History of <video> element==
<source src="A-TDHP-NEW_mpeg2video_mpeg4_VP8.webm" type="video/webm" />
The <video> element was proposed by [[Opera Software]] in February 2007.<ref>{{cite mailing list |url = http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-February/009702.html |title= &#91;whatwg&#93; &lt;video&gt; element proposal |date=28 February 2007 | accessdate=2010-04-10 |mailinglist= What Working Group |last=van Kesteren |first = Anne}}</ref> Opera also released a preview build that was showcased the same day,<ref>{{cite web | title= Browser War: Episode II – Attack of the DOMs | url = http://browserwarii.eventbrite.com/ |accessdate=10 April 2012}}</ref><ref>{{cite web |title= SV Web Builders Event – World Premier of Opera with builtin video support |url = http://coolastory.blogspot.com/2007/03/sv-web-builders-event-world-premier-of.html | accessdate = 10 April 2012}}</ref> and a manifesto that called for video to become a first-class citizen of the web.<ref>{{cite web | title = A Call for Video on the Web |url=http://people.opera.com/howcome/2007/video/ |accessdate= 10 April 2012}}</ref>
</video>


==<video> element examples==
==<video> element examples==

Revision as of 00:38, 26 August 2013

HTML
Comparisons

The HTML5 draft specification introduced the video element for the purpose of playing videos or movies,[1] partially replacing the object element. HTML5 video is intended by its creators to become the new standard way to show video on the web without plugins, but has been hampered by lack of agreement as to which video formats should be supported in web browsers.

http://gigisanchezonline.webs.com/bibliography<video controls="controls" autoplay="autoplay">

</video>

<video> element examples

The following HTML5 code fragment will embed a WebM video into a web page. 

<video src="movie.webm" poster="movie.jpg" controls>
	This is fallback content to display if the browser
	does not support the video element.
</video>

The "controls" attribute enables the browser's own user interface for controlling playback. Alternatively, playback can be controlled with JavaScript, which the web designer can use to create a custom user interface. The optional "poster" attribute specifies an image to show in the video's place before playback is started. Its purpose is to be representative of the video.

Multiple sources

Video format support varies among browsers (see below), so a web page can provide video in multiple formats. For other features, browser sniffing is used sometimes, which may be error prone: any web developer's knowledge of browsers will inevitably be incomplete or not up-to-date. The browser in question "knows best" what formats it can use. The "video" element supports fallback through specification of multiple sources. Using any number of <source> elements, as shown below, the browser will choose automatically which file to download. Alternatively, the JavaScript canPlayType() function can be used to achieve the same. The "type" attribute specifies the MIME type and possibly a list of codecs, which helps the browser to determine whether it can decode the file. Even with only one choice, such hints may be necessary to a browser for querying its multimedia framework for third party codecs. 

<video poster="movie.jpg" controls>
	<source src="movie.webm" type='video/webm; codecs="vp8.0, vorbis"'/>
	<source src="movie.ogg" type='video/ogg; codecs="theora, vorbis"'/>
	<source src="movie.mp4" type='video/mp4; codecs="avc1.4D401E, mp4a.40.2"'/>
	<p>This is fallback content</p>
</video>

Supported video formats

See also: Use of Ogg formats in HTML5

The current HTML5 draft specification does not specify which video formats browsers should support. User agents are free to support any video formats they feel are appropriate, but content authors cannot assume that any video will be accessible by all complying user agents, since user agents have no minimal set of video formats to support.

The HTML5 Working Group considers it desirable to specify at least one video format which all user agents (browsers) should support. The ideal format in this regard would:

  • Have good compression, good image quality, and low decode processor use.
  • Be royalty-free.
  • In addition to software decoders, a hardware video decoder should exist for the format, as many embedded processors do not have the performance to decode video.

Initially, Ogg Theora was the recommended standard video format in HTML5, because it was not affected by any known patents. But on December 10, 2007, the HTML5 specification was updated,[2] replacing the reference to concrete formats:

User agents should support Theora video and Vorbis audio, as well as the Ogg container format.

with a placeholder:[3]

It would be helpful for interoperability if all browsers could support the same codecs. However, there are no known codecs that satisfy all the current players: we need a codec that is known to not require per-unit or per-distributor licensing, that is compatible with the open source development model, that is of sufficient quality as to be usable, and that is not an additional submarine patent risk for large companies. This is an ongoing issue and this section will be updated once more information is available.[4]

The result has been the polarisation of HTML5 video between industry-standard, ISO-defined but patented formats, and free, open formats.

Non-free formats

See also: H.264/MPEG-4 AVC

H.264/MPEG-4 AVC is widely used, and has good speed, compression, hardware decoders, and video quality, but is patent-encumbered.[5] Users of H.264 need licenses either from the individual patent holders, or from the MPEG LA, a group of patent holders including Microsoft and Apple, except for some Internet broadcast video uses.[6]

In June 2009, the WHATWG concluded that no existing format was suitable as a specified requirement.[7]

Apple and Microsoft support only H.264[citation needed].

Free formats

See also: Theora and WebM

Although Theora is not affected by known patents, Apple[8] is concerned about unknown patents that might affect it, whose owners might be waiting for a corporation with extensive financial resources to use the format before suing.[9][10] Formats like H.264 might also be subject to unknown patents in principle, but they have been deployed much more widely and so it is presumed that any patent-holders would have already made themselves known. Apple has also opposed requiring Ogg format support in the HTML standard (even as a "should" requirement) on the grounds that some devices might support other formats much more easily, and that HTML has historically not required particular formats for anything.[10]

Some web developers criticized the removal of the Ogg formats from the specification.[11] A follow-up discussion also occurred on the W3C questions and answers blog.[12]

Mozilla and Opera support only the open formats of Theora and WebM. Google has stated its intention to remove support for H.264.[citation needed] Although it has been removed from Chromium, it has yet to be removed from Google Chrome.

Google purchase of On2

Google's acquisition of On2 in 2010 resulted in its acquisition of the VP8 video format. Google has provided a royalty-free license to use VP8.[13] Google also started WebM, which combines the standardized open source VP8 video codec with Vorbis audio in a Matroska based container. The opening of VP8 was welcomed by the Free Software Foundation.[14]

When Google announced in January 2011 that it would end native support of H.264 in Chrome,[15] criticism came from many quarters including Peter Bright of Ars Technica[16] and Microsoft web evangelist Tim Sneath, who compared Google's move to declaring Esperanto the official language of the United States.[17] However, Haavard Moen of Opera Software strongly criticized the Ars Technica article[18] and Google responded to the reaction by clarifying its intent to promote WebM in its products on the basis of openness.[19]

After the launch of WebM, Mozilla and Opera have called for the inclusion of VP8 in HTML.[20]

On March 7, 2013, Google Inc. and MPEG LA, LLC announced agreements covering techniques that "may be essential" to VP8, with Google receiving a license from MPEG LA and 11 patent holders, and MPEG LA ending its efforts to form a VP8 patent pool.[21][22][23][24]

Browser support

Main article: Comparison of layout engines (HTML5 Media)

This table shows which video formats are likely to be supported by a given user agent. Most of the browsers listed here use a multimedia framework for decoding and display of video, instead of incorporating such software components. It is not generally possible to tell the set of formats supported by a multimedia framework without querying it, because that depends on the operating system and third party codecs.[25] In these cases, video format support is an attribute of the framework, not the browser (or its layout engine), assuming the browser properly queries its multimedia framework before rejecting unknown video formats. In some cases, the support listed here is not a function of either codecs available within the operating system's underlying media framework, or of codec capabilities built into the browser, but rather could be by a browser add-on that might, for example, bypass the browser's normal HTML parsing of the <video> tag to embed a plug-in based video player.

The video format can be specified by MIME type in HTML (see example). MIME types are used for querying multimedia frameworks for supported formats.[26]

Of these browsers, only Firefox and Opera employ libraries for built-in decoding. In practice, Internet Explorer and Safari can also guarantee certain format support, because their manufacturers also make their multimedia frameworks. At the other end of the scale, Konqueror has identical format support to Internet Explorer when run on Windows, and Safari when run on Mac, but the selected support here for Konqueror is the typical for GNU/Linux, where Konqueror has most of its users. In general, the format support of browsers is much dictated by conflicting interests of vendors, specifically that Media Foundation and QuickTime support commercial standards, whereas GStreamer and Phonon cannot legally support other than free formats by default on the free operating systems that they are intended for.[27]

Browser Operating system Latest stable release Video formats supported
Theora H.264 VP8 (WebM) VP9 (WebM)
Android browser Android Template:Latest stable software release/Android (operating system) 2.3[28] 3.0[28] 2.3[28] No
Chromium All supported — r18297[29] Manual install[note 1] r47759[31] r172738[32]
Google Chrome
Windows, macOS, Linux124.0.6367.155/156[33] Edit this on Wikidata / 7 May 2024; 2 days ago (7 May 2024)
Windows Server 2012/2012 R2109.0.5414.165[34] / 13 September 2023; 7 months ago (2023-09-13)
Android124.0.6367.159[35] Edit this on Wikidata / 7 May 2024; 2 days ago (7 May 2024)
iOS125.0.6422.33[36] Edit this on Wikidata / 8 May 2024; 1 day ago (8 May 2024)
Extended Support Release124.0.6367.155[33] Edit this on Wikidata / 7 May 2024; 2 days ago (7 May 2024)
 3.0[37][38] 3.0[38][note 2] 6.0[40][41] 29.0 (Nightly)[note 3]
Internet Explorer Windows Template:Latest stable software release/Internet Explorer Manual install[note 4] 9.0[45] Manual install[note 5] No
Windows Phone 11.0 (February 10, 2014; 10 years ago (2014-02-10)) [±] No 9.0[citation needed] No
Windows RT 10.0 10.0[citation needed]
Konqueror All supported Template:Latest stable software release/Konqueror 4.4[note 6]
Mozilla Firefox Windows 7+
Standard125.0.3[49] Edit this on Wikidata / April 29, 2024; 10 days ago (April 29, 2024)
Extended support release115.10.0esr[50] Edit this on Wikidata / April 16, 2024; 23 days ago (April 16, 2024)
 3.5[51] 21.0[note 7] 4.0[54][55]
Windows Vista 22.0[56]
Linux 24.0 (Nightly)[note 8]
Android 17.0[58]
All other supported No
Opera All supported 100.0.4815.21 (June 20, 2023; 10 months ago (2023-06-20)[59][60][61])


10.50[62] No 10.60[63][64]
Safari iOS Template:Latest stable software release/Safari No 3.1[65][66] No
MacOS X Manual install[note 9] Manual install[67]
Web (previously Epiphany) All supported 45.0[68] (20 September 2023; 7 months ago (2023-09-20)) [±] 2.28[note 10]
Notes
  1. ^ Third-party codec packages are available.[30]
  2. ^ On 11 January 2011 the removal of support for H.264 was announced on Chromium Blog.[39] As of 8 September 2012 neither actual support was removed, nor the change to this plan was announced.
  3. ^ VP9 support in 25, turned off by default.[42] Enabled by default in version 29.[43]
  4. ^ Third-party codec packages are available.[44]
  5. ^ Possible if the user has installed a VP8 codec on Windows for IE9.[46][47]
  6. ^ Any format supported by Phonon on Qt 4.5.[48] Any format supported by Phonon backend. Available Phonon backends include DirectShow, QuickTime, GStreamer and xine; backends using MPlayer and VLC are in development.
  7. ^ As of version 20, prefed off by default.[52] Enabled by default beginning in version 21.[53]
  8. ^ As of version 24, disabled by default. Also, depends on the codec on the system.[57]
  9. ^ Supported if XiphQT is installed.
  10. ^ Any format supported by GStreamer on Webkit/GTK+.[69] The support for Ogg Theora, WebM and h.264 formats is included with base, bad, and ugly plugins respectively.[70]

Usage

As of April 2010, in the wake of Apple iPad launch, a number of high-profile sites have started to serve H.264 HTML5 video instead of Flash for user-agents identifying as iPad.[71]

As of May 2010, HTML5 video is not currently as widespread as Flash videos, though recent rollouts of experimental HTML5-based video players from DailyMotion (using Ogg Theora and Vorbis format),[72] YouTube (using the H.264 and WebM formats),[73] and Vimeo (using the H.264 format)[74] suggest that interest in adopting HTML5 video is increasing.

Some major video-providing websites have announced decisions to continue using technologies other than HTML5 video.[75][76][77] According to a YouTube blog post from June 2010, the <video> tag "does not currently meet all the needs of a website like YouTube".[78] The main reasons stated include the lack of a standard format, the absence of an effective and reliable means of delivering the video to the browser, JavaScript unable to display video fullscreen, and content protection issues. Hulu also has not adopted HTML5 video due to the inability of providing the user with adaptive bandwidth videos, securing the producer's content, and providing advertisers with data.[79] Netflix stated that there are a number of issues preventing them from using HTML5 video: acceptable A/V container formats; acceptable audio and video codecs; streaming protocol; a way for the streaming protocol to adapt to available bandwidth; a way of conveying information about available streams and other parameters to the streaming player module; a way of supporting protected content; and a way of exposing all this functionality into HTML5.[76][80]

On January 11, 2011, Google's Chromium Project announced on their blog that support for closed codecs (particularly H.264) would be removed from future releases of Chrome. The Chromium announcement specifically mentioned that this removal was an effort to increase the use of license-free HTML5 and the <video> tag, driving web-wide adoption of the open-source codecs VP8 and Theora. On February 2, 2011 Microsoft released the Windows Media Player HTML5 Extension for Chrome for Windows 7 which added the ability to use the licensed H.264 player included with Windows 7 to play back H.264 media content using Chrome.[81]

See also

References

  1. ^ "The video element". HTML5: A vocabulary and associated APIs for HTML and XHTML. World Wide Web Consortium. 24 June 2010. Retrieved 2010-09-27. A video element is used for playing videos or movies.
  2. ^ Hickson, Ian (10 December 2007). "Video codec requirements changed". What WG (Mailing list). Retrieved 2008-02-25. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  3. ^ "(X)HTML5 Tracking". HTML5. Retrieved 2009-06-23.
  4. ^ Amador, Manuel (2011-12-11). "Removal of Ogg is *preposterous*". WHATWG (Mailing list). Retrieved 2009-08-25. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  5. ^ "AVC/H.264 Patent List" (PDF). MPEG LA. 2010-02-01.
  6. ^ AVC/H.264 Licensors, MPEG LA
  7. ^ Hickson, Ian (2009-06-29). "Codecs for <audio> and <video>". WHATWG (Mailing list). {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  8. ^ "Steve Jobs: mystery patent pool to attack Ogg Theora". The Register. Retrieved 9 July 2011.
  9. ^ Hickson, Ian (2007-12-11). "Re: Removal of Ogg is *preposterous*". WHATWG (Mailing list). Retrieved 2008-02-25. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  10. ^ a b Stachowiak, Maciej (2007-03-21). "Codecs (was Re: Apple Proposal for Timed Media Elements)". WHATWG (Mailing list). {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  11. ^ "[whatwg] Removal of Ogg is *preposterous*". WHATWG (Mailing list). 2007-12-11. Retrieved 2009-08-25. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  12. ^ Connolly, Dan (December 18, 2007). "When will HTML 5 support <video>? Sooner if you help". W3C. Retrieved 2009-06-23.
  13. ^ Google. "Additional IP Rights Grant (Patents)". Google. {{cite web}}: |author= has generic name (help)
  14. ^ Lee, Matt (May 19, 2010). "Free Software Foundation statement on WebM and VP8". FSF.
  15. ^ Jazayeri, Michael 'Mike'. "HTML Video Codec Support in Chrome". The Chromium Blog.
  16. ^ Bright, Peter (2011-01-12). "Google's dropping H.264 from Chrome a step backward for openness". Ars Technica.
  17. ^ Sneath, Tim (2011-01-11). "An Open Letter from the President of the United States of Google". MSDN blogs.
  18. ^ Moen, Haavard K (2011-01-13). "Is the removal of H.264 from Chrome a step backward for openness?". My Opera.
  19. ^ Jazayeri, Michael 'Mike' (2011-01-14). "More about the Chrome HTML Video Codec Change". Chromium blog.
  20. ^ Metz, Cade (2010-05-28). "Mozilla and Opera call for Google open codec in HTML5 spec". The Register.
  21. ^ djwm (2013-03-07). "Google and MPEG LA make a deal over VP8 codec - Update". The H Open. Heise Media UK. Retrieved 2013-04-03.
  22. ^ http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/88/n-13-03-07.pdf
  23. ^ "VP8 and MPEG LA". WebM Project blog. 2013-03-07. Retrieved 2013-04-03.
  24. ^ http://www.fosspatents.com/2013/03/patent-clouds-remain-over-vp8-google.html
  25. ^ "Phonon documentation of backends", Qt, Nokia, retrieved 2011-06-03
  26. ^ "Phonon documentation of querying", Qt, Nokia, retrieved 2011-06-03
  27. ^ "GNU GPL - GNU General Public License Version 3 Free Software Foundation", 29 June 2007 http://www.gnu.org/licenses/gpl.html, retrieved 2013-04-27 {{citation}}: Missing or empty |title= (help)
  28. ^ a b c Kyrnin, Jennifer, Understanding HTML5 Video Formats, About, retrieved 2012-01-01
  29. ^ Issue 4363: [HTML5-Video] Enable HTML5 video/audio elements, Google, retrieved 2010-09-10
  30. ^ "Get Chromium on Ubuntu To Play MP4, H.264, MP3 & view PDF files natively", OMG Ubuntu, 2010-11-21, retrieved 2011-11-12
  31. ^ "Issue 2093007: Chromium side changes for enabling VP8 and WebM support", Code review, Google, retrieved 2010-09-10
  32. ^ http://src.chromium.org/viewvc/chrome?view=rev&revision=172738
  33. ^ a b "Stable Channel Update for Desktop". 7 May 2024. Retrieved 7 May 2024.
  34. ^ "Stable Channel Desktop Update". 13 September 2023. Retrieved 14 September 2023.
  35. ^ "Chrome for Android Update". 7 May 2024. Retrieved 7 May 2024.
  36. ^ "Chrome Stable for iOS Update". 8 May 2024. Retrieved 8 May 2024.
  37. ^ "Google Chrome support Theora and Vorbis", Code, Google, 2010-05-20
  38. ^ a b Google Chrome 3.0 will support <video> tag, FR: C net
  39. ^ Mike, Jazayeri (11 January 2011). "Chromium Blog: HTML Video Code Support in Chrome". The Chromium Blog. Retrieved 22 April 2012.
  40. ^ Bankoski, Jim (2010-05-19), "WebM and VP8 land in Chromium", Chromium (World Wide Web log), Google
  41. ^ Kersey, Jason (2010-06-03), "Dev Channel Update", Chrome Releases, Google, retrieved 2010-07-01
  42. ^ Chrome Adds Support for the Next-Generation VP9 Video Codec and Mozilla's Opus Audio
  43. ^ Chrome Now Supports Google's Next-Gen VP9 Video Codec by Default
  44. ^ Paul, Ryan (2010-02-05), "Nuanti brings HTML5 and Ogg Theora video to Silverlight", Ars Technica, retrieved 2012-01-02
  45. ^ McCracken, Harry (2010-03-16), Microsoft Previews the Revamped Internet Explorer 9 Platform, Technologizer
  46. ^ Jazayeri, Mike (2011-01-14), More about the Chrome HTML Video Codec Change, Google
  47. ^ Hachamovitch, Dean (2010-05-19), Another Follow-up on HTML5 Video in IE9, Microsoft
  48. ^ Vestbø, Tor Arne (2008-05-13), Top Secret, Hush Hush!, Nokia, retrieved 2010-03-14
  49. ^ "Firefox 125.0.3, See All New Features, Updates and Fixes". 29 April 2024. Retrieved 30 April 2024.
  50. ^ "Firefox ESR 115.10.0, See All New Features, Updates and Fixes". 16 April 2024. Retrieved 16 April 2024.
  51. ^ Firefox 3.5 (release notes), Mozilla, 2009-06-30, retrieved 2010-02-15
  52. ^ Bug 799315 – Windows Media Foundation backend for media playback, Mozilla, retrieved 2012-12-21
  53. ^ Bug 837859 – Enable WMF backend, Mozilla, retrieved 2013-04-05
  54. ^ Bug 566243 – Merge mozilla-webmedia repository to mozilla-central, Mozilla
  55. ^ Firefox Nightly Builds, Mozilla
  56. ^ Bug 825153 - Add support for Windows Vista WMF and prepend the system32 directory path to dll names, Mozilla, retrieved 2013-03-28
  57. ^ Bug 794282 - Enable GStreamer in official builds, Mozilla, retrieved 2013-06-23
  58. ^ http://arstechnica.com/information-technology/2012/11/mozilla-ships-firefox-with-h-264-support-on-android/
  59. ^ "Thanks for downloading Opera". Opera Norway. Retrieved 21 June 2023.
  60. ^ "Thanks for downloading Opera". Opera Norway. Retrieved 21 June 2023.
  61. ^ "Index of /ftp/pub/opera/desktop/100.0.4815.21/". Opera Norway. Retrieved 21 June 2023.
  62. ^ Jägenstedt, Philip (2009-12-31), "(re-)Introducing <video>" (official blog), Core developers, Opera, retrieved 2010-02-06
  63. ^ Lie, Håkon Wium (2010-05-19), Welcome, WebM <video>!, Opera
  64. ^ Mills, Chris (2010-05-19), Opera supports the WebM video format, Opera
  65. ^ "HTML5 video formats", Web design, About.
  66. ^ "Media formats supported by the HTML audio and video elements", Developer, Mozilla.
  67. ^ "WebM plugin available", Code, Google, retrieved 2011-06-23
  68. ^ "Introducing GNOME 45". 20 September 2023. Retrieved 21 September 2023.
  69. ^ Persch, Christian (April 01, 2008), "The Future of Epiphany" (announcement), epiphany mailing list-list {{citation}}: Check date values in: |date= (help)
  70. ^ "Overview of available plug-ins", GStreamer, retrieved 2012-07-04
  71. ^ "iPad-ready websites". Apple. Retrieved 2010-04-05.
  72. ^ "Watch Video… without Flash". Dailymotion. 2009-05-27. Retrieved 2010-05-18.
  73. ^ Carle, Kevin; Zacharias, Chris (2010-01-20). "Introducing YouTube HTML5 Supported Videos". Youtube. Google. Retrieved 2010-03-07.
  74. ^ Dougherty, Brad (2010-01-21). "Try our new HTML5 player!". Vimeo. Retrieved 2010-03-07.
  75. ^ Herrman, Johan (2010-02-03). "Giz Explains: Why HTML5 Isn't Going to Save the Internet". Gizmodo. Retrieved 2012-07-25.
  76. ^ a b "Netflix has no plans to use HTML5", Gigaom.
  77. ^ "Why HTML5 won't replace Flash", Pseudocoder.
  78. ^ "Flash and the HTML5 <video> tag". You tube. Google.
  79. ^ "Pardon Our Dust <video> tag". Hulu. 2010‐5‐13. {{cite web}}: Check date values in: |date= (help)
  80. ^ "Netflix working on HTML5 streaming", PCMag.
  81. ^ Caldato, Claudio (2011-02-02). "Greater Interoperability for Windows Customers With HTML5 Video" (blog). MSDN. Microsoft. Retrieved 2012-07-25.

External links

Retrieved from "https://en.wikipedia.org/w/index.php?title=HTML_video&oldid=570196721"