HTML5 Rocks: A resource for open web developers

http://blog.chromium.org/2010/06/html5-rocks-resource-for-open-web.html

by nswanberg • 16 years ago

147 31 16 years ago

blog.chromium.org

ugh2• 16 years ago

Apple’s: http://developer.apple.com/safaridemos/ (Much more polish and probably intentionally unaware of every browser except Safari.)

Aren’t you all just loving our new browser arms races? Everyone wins.

mbrubeck• 16 years ago

http://hacks.mozilla.org/ and http://dev.opera.com/ and http://ie.microsoft.com/testdrive/ have similar content from the other big vendors.

BonoboBoner• 16 years ago

I love it, but at the same time I am scared of the fragmentation of web technologies this could result in. Bigger specs means more room for companies to do mistakes, to include inconsistencies...

ugh2• 16 years ago

That could happen but I somehow think that’s still better than those five horrific years after 2001 before Microsoft brought out Internet Explorer 7.

krav• 16 years ago

Next up, Adobe launches FlashZings.

BenSchaechter• 16 years ago

HTML5 makes me thoroughly excited for the not-so-distant future web. From both an end-user and developer perspective.

seiji2• 16 years ago

I adapted their HTML5 slideshow interface into a comic viewer: http://slippycomics.com/

Pretty nifty for viewing old comics linearly. Works okay-ish on an iPad too (click for alt-text/alt-comic).

Background/introduction: http://matt.io/slippycomics/introducing_slippycomics

samratjp• 16 years ago

Pretty cool, but man it's annoying though to press back button. Wish it were more ajaxy.

jeff182• 16 years ago

Nice. I made something pretty similar here: http://www.wolfire.com/comic

seiji2• 16 years ago

Your version is quite nice. Great design. Looks like you have the added benefit of pre-knowing your comic dimensions.

You're afflicted with the non-functioning-hashes-in-history problem though. This fixed it for me: http://github.com/tkyk/jquery-history-plugin

Though, it does get annoying ending up with 100 non-pages in your history. Maybe a big "navigate by hashes: yes/no" option would help us out.

d0m• 16 years ago

Funny how it says firefox isn't supported in some tutorials!

sayrer2• 16 years ago

Well, I wouldn't say it's funny. (disclosure: I work for Mozilla)

I don't like these sites because they mislead developers about which technologies are standards and which are not.

But don't strawman me here: I actually have no problem with browser vendors unilaterally extending HTML. I like that Opera, Google, Apple, Microsoft and various plugin vendors all try it. Sometimes great ideas show up that way (you can thank the IE team of old for the great majority of them).

It's also disturbing because it takes the name of something we all work on together and applies it to technologies where there is no agreement. And some of them really do suck! Apple and Google clearly don't care about this problem, and are happy to label whatever they work on as HTML5 (my favorite was the Unity demo during Google I/O... it was all plugins). At this point, it's safe to assume you've encountered meaningless bullshit when some VP gets up on stage and says "HTML5".

patrickaljord5• 16 years ago

They clearly said during Google IO that Unity was running on NaCl though. And this site html5rocks looks very neutral and their demos don't force you to use any browser in order to be tested unlike Apple demo.

sghael• 16 years ago

Agreed that this is all cool stuff. But as developer of a webapp that heavily leverages webcam / mic access (blatant plug: http://activeinterview.com), I'm waiting anxiously for this to get fleshed out:

http://dev.w3.org/html5/html-device/

Device access! Then we can really drop kick Flash when needing to talk to devices like webcam/microphone.

But alas, it could be a while? http://stackoverflow.com/questions/3012002/what-web-browser-...

As someone far removed from the standards bodies, how can we support this effort and push things along?

seabee• 16 years ago

I imagine the best way is to get the source of Firefox or Chromium and have a go at implementing it yourself. Things move quicker when there's code for people to look at and improve.

bad_user• 16 years ago

Why are there properties labeled with a "webkit" prefix? ... surely that's not in the HTML5 standard.

patrickaljord5• 16 years ago

That's the standard way to implement unfinished specs, firefox does the same with the "moz" prefix.

sams992• 16 years ago

Are they using bespin for the syntax highlighting in the playground?

sams992• 16 years ago

Actually, its code mirror.

rbreve• 16 years ago

html5rocks.com crashes the ipad's safari browser, and slows down safari 5 on mac osx, wonder why

ZeroGravitas2• 16 years ago

The recent Apple "HTML5" demo, the video one in particular, crashed Safari on my iPhone 3G.

Kilimanjaro• 16 years ago

Feed please!

nswanberg• 16 years ago

If you use Google Reader, try this: http://googlereader.blogspot.com/2010/01/follow-changes-to-a...

moultano• 16 years ago

Oh God. Css animations. :(

bittersweet• 16 years ago

Has anyone gotten fileuploads to work with filereader in Chrome yet? I seem to be getting "Object has no method 'addEventListener'" errors so I think that part of the spec is not fully implemented yet.

HTML5 Rocks: A resource for open web developers

Related Stories