Linked by Thom Holwerda on Fri 19th Jun 2009 15:23 UTC
Mozilla & Gecko clones We're on the verge of a serious evolution on the web. Right now, the common way to include video on the web is by use of Flash, a closed-source technology that is a massive resource hog. The answer is the HTML5 video tag, which allows you to embed video into HTML pages without the use of Flash or any other non-HTML technology; combined with open video codecs, this could provide the perfect opportunity to further open up and standardise the web. Sadly, not even Mozilla itself really seems to understand what it is supposed to do with the video tag, and actually advocates the use of JavaScript to implement it. Kroc Camen, OSNews editor, is very involved in making/keeping the web open, and has written an open letter to Mozilla in which he urges them to not use JavaScript for HTML video. Note that Kroc's website may not work properly in Internet Explorer. (Update The letter has been mirrored in the article, Read More for the full text)
E-mail Print r 27   · Read More · 65 Comment(s)
Permalink for comment 369440
To read all comments associated with this story, please click here.
In the spec
by matto1990 on Fri 19th Jun 2009 19:55 UTC
matto1990
Member since:
2009-04-18

If you read the HTML5 spec you'll see that the JavaScript is an intended part of the <video> tag.

http://www.whatwg.org/specs/web-apps/current-work/multipage/video.h...

Beware: It's long ;)

What you need to understand is that this isn't an issue with Mozilla, it's an issue with the spec - well... in your view anyway. Personally I can't see anything wrong with requiring JavaScript. The links and buttons that will be linked to the media.play() method will likely be part of the HTML document, and therefore clickable using a screen reader or some other sort of accessibility technology. Having JavScript will not stop people clicking these links.

The only problem comes is when you don't have Javascript enabled, and almost everyone has it enabled. The only people that don't are people who know what it is; and if they know what it is they are likely to know the consequences of turning it off. Most people who browse the web have no idea what JavaScript is, so they just leave everything as the default (which is on).

Personally I see this as a non-issue. As the web evolves the technology around it has to as well. If this means one web technology (HTML) becoming strongly linked to another (JavaScript) so be it. We've had far too long where the web stood still because of lack of innovation, and we're paying the price now. The only way to innovate is to evolve, and that does mean making some changes that might not seem like a brilliant idea at the time; but as the web moves on the changes that are made will become accepted and become the new standard.

PS. sorry for the long and rambling rant ;)

Reply Score: 2