<video> tag is supposed to work like a glorified
Simply put, “Video for everybody” uses the
<video> tag if your browser supports it, using OGG video. If your browser does not support it, it falls back to Flash. Is Flash not supported either? QuickTime will be used (which allows playback on the iPhone). Don’t have QuickTime either? Internet Explorer in Windows Vista and up will switch to Windows Media Player.
What Mozilla should do
Kroc asks the following of Mozilla:
Remove the content of that blog post and replace it with new content that covers two main factors:
- How to insert HTML5 video using HTML and providing levels of fallback for legacy systems
Adopt HTML5 video (with fallbacks) across all Mozilla branded blogs, sites and web properties, unilaterally
- I personally don’t have Flash installed, it is – after all – an optional install, and I don’t like what it does to my computer. It seems counter to the work you are doing providing HTML5 video in your browser that I cannot see your own announcements.
- I believe Mozilla need to make a company-wide (and community-wide) commitment to using HTML5 video in all of their ventures – past, present and future.
Personally, I support Kroc’s open letter, and he hopes that more of you will do so. If you agree with Kroc that the
<video> should be used properly, and that it is important to move towards a web that is more open and more standardised than it is now, you can contact Kroc (Twitter | e-mail) to have your name added to the list of undersigned. In addition, you can spread the word, and propagate Kroc’s open letter to Mozilla, Video for Everybody, or this OSNews item across the web.
The Letter (Mirror): An Open Letter to Mozilla Regarding Their Use and Promotion of HTML5 Video
HTML5 video is coming, and a million web developers up and down the web will be soon looking for advice
and sample code to make use of HTML5 video. Web developers vary massively in skill and understanding of
the open principles of web development, promoted by yourselves via the
We cannot expect all developers to understand the knock-on effect of code snippets that they are copy-pasting from
people’s sites. It is one thing to educate people with a piece of code, it is another to communicate effectively
the principles behind a piece of code. Some developers do not care, and never willâ€”that is a fact of life.
developers a number of major drawbacks, counter-intuitive to the points outlined in the Mozilla Manifesto.
browsers that developers are very unlikely testing in, who may inadvertedly break support by using
In other blog posts you have promoted the
<video>element as a glorified
<img>elementâ€”being fundamentally a part of the document with all the same
capabilities CSS-wise. Some
incredible examples have been
demonstrated that go well beyond what is possible with plugins.
bad code be responsible if so), the same should be true of video.
sites that they may otherwise not trust. Viruses and malware have travelled far by hiding behind videos, and
they can see a video.
- Non-aggregatable, mashable
format, HTML goes beyond just the traditional â€˜web-browser’ and may be parsed in
many ways and environments outside of the traditional browser.
as a safety measure, thus preventing the user from seeing the content.
Robots and spiders also would not be able to spider HTML5 video content if it is only
cannot yet conceive. What if a TV station could be created using nothing but
<video>largely puts a stop to mash-ups wanting to pull video from the web.
A Solution Has Been Presented
A solution for using HTML5 video with fallbacks for Adobe Flash, QuickTime and
has been developed, it’s called â€œVideo for Everybodyâ€.
The market is made up of more OSes, browsers and processor architectures than it was five years
ago. More people (especially geeks) are browsing with AdBlock / NoScript /
FlashBlock than ever before. We can no longer just assume people are going to have
Flash and are allowing you to use it.
The same rules apply to video. If my platform / device / browser of choice cannot see your video, or you do
not offer me the means to download the video to view offline, then I don’t see whatever it is you’ve got
to show me.
It helps web developers promote HTML5 video as an equal citizen alongside Flash and
QuickTime. The necessary playback is chosen automatically based on browser / operating system
fallback text is displayed to offer the users a means of downloading the video file, or how to get the video to play
in the webpage by installing an HTML5-capable browser, Flash or QuickTime.
This means that it is almost impossible for the user to not be able to view the videoâ€”one way or anotherâ€”and they
native HTML tag.
What You Can Do
I ask you to please do the following:
- Remove the content of that blog post and replace it with new content that covers two main factors:
How to insert HTML5 video using HTML and providing
levels of fallback for legacy systems
Why providing good fallback options / text is so important to a range of users
enhance a solution rather than be a requirement
- Adopt HTML5 video (with fallbacks) across all Mozilla branded blogs, sites and web properties, unilaterally
I personally don’t have Flash installed, it isâ€”after allâ€”an optional install,
and I don’t like what it does to my computer. It seems counter to the work you are doing
providing HTML5 video in your browser that I cannot see your
I believe Mozilla need to make a company-wide (and community-wide) commitment to using
HTML5 video in all of their venturesâ€”past, present and future.