Tried it in Chrome, and I'm hella impressed. Everybody else is busy hating on it, but I'd like to thank the developers for putting it together. That 20 minutes of playtime has taught me 10 times as much about what to expect (and why I should be excited) than all the discussions and blog posts I've seen so far.
So, while some things didn't work, I'm not going to harp or nag, as overall the presentation was excellent.
Re:HTML5 presentation
by Tycho on Saturday April 17, 2010 @10:43AM
(#1273093)
It was fantastic (on Chrome anyway). Incidentally that 'press arrow key for next page' feature is something I've wished all websites had for a long time - like to leaf through forum pages or article pages.
Re:HTML5 presentation
by zsouthboy on Saturday April 17, 2010 @01:29PM
(#1273355)
Opera has a "Next Page" feature that is usually able to do exactly what you ask on most sites/forums.
Also, it's smart about it - if you're on a page that it's remembered a username/password for, if you go Next Page (either the mouse gesture or left/right mouse rocker gesture), it'll log you in automatically.
Re:HTML5 presentation
by grandalf on Saturday April 17, 2010 @12:25PM
(#1273253)
the point was to make you click and then realize it's keyboard nav... i thought it was clever. If they made it clickable nobody would have noticed the keyboard nav.
Re:HTML5 presentation
by lambda on Saturday April 17, 2010 @01:36AM
(#1272677)
Cool demo, but it's a bit odd to tout new, standard features, when you have a disclaimer that this is only intended to completely work in Google Chrome with experimental features enabled. Part of the excitement is that these features are being standardized, and aren't just one vendor wandering off and doing their own thing without consulting with anyone else.
What would be far more impressive would be a demo that worked seamlessly in Firefox, Safari, Chrome, Opera, and IE with Chrome Frame, with graceful degradation (or, preferably, progressive enhancement) for features which aren't implemented yet in IE without Chrome Frame (and the features that aren't yet fully supported cross-browser).
Re:HTML5 presentation
by andrewtj on Saturday April 17, 2010 @04:34AM
(#1272818)
This is a demo of what's at the bleeding edge. To complain that it's not implemented across all browsers with graceful degradation is to be frank, silly.
Re:HTML5 presentation
by rimantas on Saturday April 17, 2010 @06:04AM
(#1272860)
Too bad that navigation model chosen does not allow to browse the presentation on iPhone/iPad. Many of those advanced features (session/local/web SQL DB storage, geolocation, CSS transforms/transitions/animations, offline web apps) are supported in Mobile Safari—in fact some appeared there first.
Re:HTML5 presentation
by dinde on Saturday April 17, 2010 @12:54AM
(#1272642)
This is extremely cool. I admit it scared me a little bit just how easy it was to do the geolocation. The web is about to change dramatically, again. :)
Re:HTML5 presentation
by ashleyw on Saturday April 17, 2010 @07:30AM
(#1272927)
Does anyone know where GeoLocation gets the data? My IP is registered to a city 35 miles away, yet it's able to pinpoint where I am within a few meters?
Re:HTML5 presentation
by ugh on Saturday April 17, 2010 @08:27AM
(#1272954)
«There are a few common ways to get location information. The most common are local WiFi networks, IP address information, and attached GPS devices. In Firefox 3.5 we use local WiFi networks and IP address information to try and guess your location.»
Re:HTML5 presentation
by andrewtj on Saturday April 17, 2010 @04:27AM
(#1272811)
It's a tech demo designed for Chrome — a pretty reasonable compromise given it's supposed to show what's coming up in browsers and requires Chrome be invoked with various command line flags to demo all the features.
Re:HTML5 presentation
by jared314 on Friday April 16, 2010 @11:48PM
(#1272579)
Awesome. It doesn't work on the Droid, because of the arrow key requirement.
I also think it is missing a position-in-presentation indicator, like a progressbar or a smaller zoomed out version along the bottom.
Re:HTML5 presentation
by stanleydrew on Saturday April 17, 2010 @11:14AM
(#1273142)
I think you'll need to use the --enable-webgl command line switch to turn it on. I'm not sure that will work in anything besides the latest dev channel builds though.
Re:HTML5 presentation
by daeken on Saturday April 17, 2010 @01:59AM
(#1272702)
Not quite true. Each page has its own anchor, so making the back button work properly is pretty trivial. That's a big oversight in an otherwise awesome presentation.
Very nice. Not very FF friendly but still very nice. I am liking how the web will be in the coming future. Only need all browser vendors to get their act together and get standards compliant. Microsoft can be augmented with Chrome frame so the one hindering block can be ignored.
Re:HTML5 presentation
by whalesalad on Saturday April 17, 2010 @12:19AM
(#1272609)
FF is quickly becoming an obsolete browser. iPhone uses Webkit, iPod Touch, iPad, every single Android phone (like the Nexus One and Droid), Chrome on Windows & Mac... every new Mac... the list goes on. I'm all for competition, but Webkit is clearly the champion here.
Re:HTML5 presentation
by mgcross on Saturday April 17, 2010 @12:36AM
(#1272633)
FF is hardly obsolete. The presentation used vendor-specific extensions (-webkit-) that are not part of the CSS3 spec, much less HTML5. Many of the features could have been implemented in FF had the author used -moz- alongside -webkit-.
Re:HTML5 presentation
by devinj on Saturday April 17, 2010 @12:29AM
(#1272626)
That's nice and all, but Firefox is still one of the biggest browsers out there. It's not obsolete, and you can't ignore it if you value users. In fairness, not everyone values users.
So, while some things didn't work, I'm not going to harp or nag, as overall the presentation was excellent.
Except for mobile browsers without a right arrow key.
What would be far more impressive would be a demo that worked seamlessly in Firefox, Safari, Chrome, Opera, and IE with Chrome Frame, with graceful degradation (or, preferably, progressive enhancement) for features which aren't implemented yet in IE without Chrome Frame (and the features that aren't yet fully supported cross-browser).
– http://hacks.mozilla.org/2009/06/geolocation/
though i didn't get the last comment about IE6. I tried loading the url in IE6 twice, and both times the browser crashed.
Chrome 5.0.342.9 (beta) does not seem to be.
Chrome can be with a runtime flag.
FireFox has an about:config flag.
here it is in the CSS2.1 spec -- http://www.w3.org/TR/CSS2/visuren.html#display-prop
it looks like it was introduced in CSS 2.1 because it is missing in CSS2 and CSS1: http://www.w3.org/TR/2008/REC-CSS2-20080411/visuren.html#dis... http://www.w3.org/TR/REC-CSS1/#display
Is this expected of HTML5?
That said, I hope Adobe is scared as hell--and more importantly, that they get their act together... or else.
2. Transition flash creationg tools to HTML5 creation tools
voila - relevance
That doesn't seem like broken behavior to me.