Currently, Firefox web developers use the Firebug add-on to achieve the same effect. Cambell has stated Mozilla is not out to “kill” the Firebug add-on, but to merely suplement it.

“Now every browser ships with a set of development tools. We didn’t feel that [the original] DOM Inspector was the right tool to include in the browser” wrote Cambell.

Early Firefox 4 builds that include the new, unfinished DOM inspector are available for download.

“When it comes to technology, our only guiding principle is to best serve the needs of all of our key customers: our viewers, our content partners who license programs to us, our advertisers, and each other. We continue to monitor developments on HTML5, but as of now it doesn’t yet meet all of our customers’ needs. Our player doesn’t just simply stream video, it must also secure the content, handle reporting for our advertisers, render the video using a high performance codec to ensure premium visual quality, communicate back with the server to determine how long to buffer and what bitrate to stream, and dozens of other things that aren’t necessarily visible to the end user. Not all video sites have these needs, but for our business these are all important and often contractual requirements” wrote Eugene Wei, VP of Product at Hulu.

With Apple putting all its eggs in the HTML5 basket, it seems others aren’t so sure. Adobe’s concerns appear valid, and today launched its We Love Choice campaign.

“At Adobe, we believe that the open flow of creativity, ideas, and information should be limited only by the imagination. Innovation thrives when people are free to choose the technologies that enable them to openly express themselves and access information where and when they want. Everyone loses when technological barriers impede the exchange of ideas” the campaign says.

It’s clear the HTML5 vs Flash debate is far from over.

Google has done the “impossible” to show the power of HTML5, and ported Quake II to run in the web browser in what seems another dig at Adobe’s Flash.

The move seems a little contradictory, with Google announcing just last week that they were bundling Adobe’s Flash with Chrome. Either way, a lot of work appears to have gone into porting the game.

“We started with the existing Jake2 Java port of the Quake II engine, then used the Google Web Toolkit (along with WebGL, WebSockets, and a lot of refactoring) to cross-compile it into Javascript. You can see the results in the video above — we were honestly a bit surprised when we saw it pushing over 30 frames per second on our laptops (your mileage may vary)” said Google’s Chris Ramsdale.

Right now, the game will only run in Google Chrome and Safari, and the port can be downloaded by visiting the Google code page.

Up until now, most of the HTML5 draft has been worked on by rivals Apple, Mozilla, Opera and Google.

According to reports, Internet Explorer Program Manager Adrian Bateman has sent a letter to the World Wide Web Consortium, with Microsoft’s thoughts and queries on the current editor’s draft.

“As part of our planning for future work, the IE team is reviewing the current editor’s draft of the HTML5 spec and gathering our thoughts. We want to share our feedback and discuss this in the working group. I will post our notes as we collect them so we can iterate on our thinking more quickly. At this stage we have more questions than answers, but I believe that discussing them in public is the best way to make progress” said a letter from Bateman.

Microsoft hasn’t completely ignored HTML5, with Internet Explorer 8 including support for the DOM Store, Ajax Navigation, Cross Document Messaging and Cross Domain Messaging, all components of  HTML 5.

More developments are sure to continue.

Berners-Lee’s idea envisioned researches being able click on links in documents to other relevant articles.

Surely the WWW is one of the greatest inventions of the last 20 years. You can read more about the WWW and Tim Berners-Lee.