Tuesday, June 22nd, 2010
Category: Browsers
, CSS
, HTML
<
p
>
The Chrome and HTML DevRel team at Google have released a new portal, HTML5 Rocks, that packages together some of the great resources available on HTML5 and the renaissance of browsers.
Whether it be references on what you can do, to readiness to shims to get use features now.

Beyond the resources, there is the killer HTML5 Slide Presentation and interactive playground.
A lot of nice stuff, all in one place. This is the first release, and we are sure to see a lot of additions coming soon. What would you like to see?
- Google Drive: Google’s new cloud service
Google’s new cloud service, Google Drive, lets users create, share, collaborate, and store files from PCs, smartphones and Android tablets, with an...
- Where's the love for Microsoft technologies?
Talk of Google, Amazon and Apple is eclipsing the once fervent buzz around Microsoft...
- Opinion: Chrome OS buffs up the Google Brand
Google's announcement that it is working on a lightweight operating system is as much about marketing as it is about...
- Security Wire Weekly: No deal for Snort, victory for Google and love versus productivity on the job
This week, a talk with Kansas City Snort User Group Founder Russ Starr on the future of Snort amid the recent collapse of the Check Point-Sourcefire...
- Security Wire Weekly: No deal for Snort, victory for Google and love versus productivity on the job
This week, a talk with Kansas City Snort User Group Founder Russ Starr on the future of Snort amid the recent collapse of the Check Point-Sourcefire...
Also, http://html5r0cks.com
I lol’d.
They’re making the same mistake as Apple. They should fix the code so it worked in Opera or Firefox. Those -webkit- prefixes mean it can only possibly be supported in Chrome / Safari.
Don’t forget http://slides.html5r0cks.com ;)
Chris,
I added -moz- and -o- prefixes for all of the playground and tutorials. Certainly it’s in the best interest of the web to use css3 properties in the most cross-browser way possible. If I missed anything in particular, please file a bug or mention it here.
so the Chrome team wants to show us how buggy their border radius is? http://i50.tinypic.com/14nuo5.png