A Blog From Behind the Trenches

Attack of the Bugs

Subscribe to RSS feed

Posts tagged with "html5"

From C++ to HTML5: Rebuilding a game using open web standards

, , , ...

Remember that cool preview of WebGL demo that Opera made for the GDC?

The demo is being made by Opera Core developer Erik Möller. He has 15 years of experience in the gaming industry, and before he started at Opera, he created an indie game called Emberwind (trailer).

Since he's working for a browser company now, he decided to get a little more familiar with various web technologies. One of his first steps was to get some hands-on experience, so he decided to recreate the logo of his indie game company using SVG.

That apparently got him thinking... What could he do next?

Read more...

Microsoft's "Native HTML5" nonsense

, , , ...

Another week, another nonsensical marketing claim from Microsoft.

This time they have tried to coin the term "Native HTML5", which basically contradicts the whole idea of the web as non-native and platform-agnostic. You know, the idea the entire web was built on?

HTML5 is not native. It is not supposed to be native. It is silly to even attempt to tie HTML5 to a specific platform.

Some people are making fun of Microsoft's antics, which is all well and good. The idea of "Native HTML5" is that ridiculous. Others are quite harsh in their coverage. I think a combined approach is necessary: Make fun of their obvious attempt to hijack HTML5, while making sure that their claims are also met with clear, factual refutations.

In my opinion, Dean Hachamovitch should be ashamed of himself for signing his name to such a shoddy piece of dishonest marketing nonsense. Call me a grumpy old open web fundamentalist, but I'm getting fed up with this.

Whew, glad to get that off my chest smile

WebM support in IE9 without browser plugins

, , , ...

The WebM project announced today that WebM support will be available in IE9 without having to use a browser plugin. While it won't be supported by default, IE9 will support the codec as long as it's available as a Windows system codec.

And just to clarify: This means that this is not just another browser plugin like Flash, but rather allows IE9 to support WebM through the HTML5 <video> element.

The inevitable question here is how this is any better than using a browser plugin, and the answer is this avoids all the limitations of browser plugins. It opens up a whole new world of possibilities, since HTML5 video can be accessed and manipulated by the browser. A browser plugin, on the other hand, is basically a "black box" to the browser. It doesn't offer even a fraction of the flexibility you get with native HTML5 video (video support in the browser itself).

As I explained in a previous blog post on the subject, this will deal another blow to the closed H.264 codec on the desktop.

So for now, I think we can ignore the hilariously hypocritical quip about "ideology" in the Microsoft blog post, and congratulate them on doing the right thing instead!

Being on the bleeding edge of open web standards ain't easy...

, , ,

Sometimes, being on the bleeding edge, and being the first to support interesting new web technologies, causes problems.

A couple of days ago, we released an Android build with support for the HTML5 <device> element. This gives you access to the phone's camera, which opens up new possibilities on the web, such as video conferencing. Our guys had been working on this for a while, and I guess they were looking forward to seeing what people would be able to do with it.

But that very same day, the decision was made to remove the <device> element from the HTML5 specification, and replace it with a JavaScript API.

The good news is that we can probably reuse quite a bit of what we did to support <device>. From what I hear, the Opera guys involved with HTML5 actually welcomed the change as well.

But this shows that being on the bleeding edge isn't always easy. Things can change quickly in the world of technology!

W3C HTML5 Test Suite description updated to avoid confusion

, , , ...

There has been a lot of confusion around the W3C HTML5 Test Suite the last couple of days. It was widely reported that because IE9 seemed to pass most of the tests (many of which are made by Microsoft), it was the most HTML5 compliant browser (which is of course not true).

The HTML5 Test Suite Conformance Results page has now been updated to clarify the situation:

The HTML5 Test Suite Results aims to help implementers write applications that support HTML5. In no way are these conformance tests to be construed as providing certification or branding of HTML5 implementations. The only claim that could be made is that a particular implementation is conformant to a particular version of the HTML5 Test Suite.

It is inappropriate to cite those results as other than work in progress and unstable.

In other words: The results of these tests do not reflect the general HTML5 compliance. They only show which browsers pass those specific tests available at that specific time.

The page also explains that the Test Suite is under development. At the moment, there is a relatively small number of tests, but this will grow over time.

Is Internet Explorer 9 the most HTML5 compliant browser? Not quite.

, , , ...

It's all over the web. IE9 is being labeled the HTML5 conformance champion, based on a set of official tests at the W3C.

PC World, for example, writes:

Internet Explorer 9 has topped all other browsers in conforming with the HTML5 specification, including Google Chrome and Firefox, according to tests carried out by the World Wide Web Consortium.

This would be quite amazing if it was true. But it isn't. You can't draw such conclusions based on those tests.

Read more...

What is HTML5?

, , ,

If you are confused about what HTML5 is and how it relates to other web technologies, Bruce Lawson has created a visual masterpiece of Michelangelian proportions to guide you.

Read more...

Did Apple weaken the case for HTML5 and strengthen Flash with their "HTML5 Showcase"?

, , ,

My blog post on Friday about Apple's "HTML Showcase", which neither used a lot of actual HTML5, nor seemed to promote HTML5 as a cross-browser standard (it even requires QuickTime, apparently), received quite a bit of attention.

Even though the blog post was written as a response to questions about why Opera and other browsers couldn't show the demos, it partially ended up as a discussion about the viability of HTML5 as a cross-browser solution! That was not my intention, nor do I believe that it was Apple's intention to send that message with their "HTML5 Showcase". I am confident that HTML5 is not only future-proof, but also a necessary step in the evolution of the web.

Read more...

Apple's new "HTML5 Showcase" doesn't show much HTML5, and is browser-specific

, , , ...

Background: Apple's new "HTML5 Showcase" is raising a few questions from Opera users (and others), so I thought I'd address them here.

Apple claim to promote HTML5 and an open Web, but the page uses browser sniffing to block other browsers, vendor prefixes for the CSS3 stuff they are using (even if other browsers support border-radius it won't work because it's coded using -webkit-border-radius), and the patent-encumbered H.264 for video.

In fact, it seems that the only things that are HTML5 on that page are HTML5 audio and video.

Read more...

Putting x264 developer's technical analysis of WebM (VP8) into perspective

, , , ...

The main x264 (H.264 encoder) developer, Jason Garrett-Glaser, has written up an interesting analysis of WebM/VP8. This analysis has gotten quite a bit of attention online, and a lot of people seem to take it as the final word on the matter.

However, as with most things, there is more than one side to this story.

Read more...

Google to open-source VP8?

, , , ...

Google is on a roll!

Just the other day they decided to throw some money at Theora, and now rumours have it that they are planning to open-source the VP8 codec!

People were wondering what the acquisition of On2 would lead to, and the FSF even asked Google to "free VP8". As you may know, On2 the maker of the VP2 codec, which Theora is based on. If VP8 ends up as open-source and not encumbered by patents thanks to Google, only good can come from that.

I really hope the rumours are true, because the Web needs all the help it can get when battling closed, patent-encumbered technologies like H.264. HTML5 video should be based on free and open technologies, at least as a common baseline.

Google really does know how to shake up existing markets, that's for sure.

Google puts it weight behind Theora

, , , ...

While Google's Chrome supports both Theora and H.264 for HTML5 video, Google chose H.264 over Theora for YouTube.

This was rather disappointing since I was hoping that Google would go for the open format. However yesterday's word from OSNews that Google is helping to fund an ARM port of Theora makes me much more optimiztic.

It seems that Google is actually saying that we do need a free and open baseline codec for the Web, and I couldn't agree more. After all, the foundation of the Web should be built on free and open standards and technologies. That's the only viable way to move the Web forward, and it wouldn't even have existed today without it.

So now Opera, Mozilla and Google all seem to be in agreement on that the foundation needs to be.

How will Apple and Microsoft respond?

And how does Google's acquisition of On2 fit into all of this?

Open letter to Microsoft regarding video on the Web

, , , ...

Dear Microsoft:

I haven't exactly cut you a lot of slack in my blog through the years. I have repeatedly criticized you for the damage I feel that you have done to the Web. But while you have traditionally been known for closed and proprietary solutions, lately you have been speaking more and more frequently and vocally about the importance of interoperability on the Web.

And today you might just have a chance to make up for your past wrongs. You have a unique opportunity to show that you are serious about interoperability and open standards!

As you may know, there is a "war" being waged about video on the Web. Some are promoting the closed, patent-encumbered H.264 codec as the best codec for the Web, while others believe that the basic building blocks of the Web should be free and open, and therefore promote Ogg Theora as the "default" codec for HTML5 VIDEO.

Currently, HTML5-capable browsers with Theora support make up a much bigger share of the market than the browsers that support H.264, but that will change if you release Internet Explorer with support for H.264 rather than Theora.

If you were to support Theora as the video codec of choice in Internet Explorer, it would be a bombshell which would not only give a huge boost for open Web technologies, but you could be seen as a champion of open standards, and an open Web.

I know you are a patent licensor in the MPEG LA, and this would actually make your actions even more powerful and meaningful. You could show just how serious you are about interoperability on the Web by supporting the free and open codec rather than the one that would best suit your short-term interests.

This is a unique opportunity for you to win back the hearts and minds of people who might have otherwise dismissed you as carrying on with "business as usual".

Are you up for it?

-Haavard

H.264 is royalty-free for Web use through 2015, but still not a good idea

, , , ...

The MPEG LA (Licensing Authority) has announced that H.264 licenses for free internet video will be free until the end of 2015.

I still don't think it's a good idea to use H.264 as the standard video codec on the Web.

Read more...

No open video for Vimeo either, so what now?

, , , ...

Hot on the heels of YouTube's failure to deliver open video, it seems that Vimeo has decided to introduce HTML5 video support as well. But like YouTube, they decided to go for a patent-encumbered and non-free video codec instead of Theora.

While this is disappointing, there are other sites out there that are more than happy to lead the way into an open future. They may not be as big as YouTube, but one can hope that their early adoption of open video technologies will give them a nice boost.

Read more...

YouTube fails to deliver on HTML5 promises

, , , ...

The vote for YouTube to support HTML5 with open video formats was a huge success.

Right now, the "Support HTML5 open web video with open formats" option has more than 12 000 votes, whereas the most popular request that is unrelated to HTML5 has about 5 000 votes. The HTML5 requests were so popular that YouTube had to hide them to give other options a chance to be seen:

We've heard a lot of feedback around supporting HTML5 and are working hard to meet your request, so stay tuned. We'll be following up when we have more information. We're answering this idea now because there are so many similar HTML5 ideas and we want to give other ideas a chance to be seen.

However...

Read more...

YouTube wants people's feedback: Opportunity for HTML5?

, , , ...

YouTube is doing some "spring cleaning", and is looking for people's feedback on what to fix.

It seems that "Support HTML5 open web video with open formats" is the highest ranked item so far. I'm really happy to see that. YouTube with HTML5 and Theora support could give open standards a huge boost!

If you would like open standards to prevail, let your voice be heard too.