As the discussion had turned into bunch (good) advice giving, I
decided to repost this if anyone actually has opinion on this matter
and/or could tell me why the spec recommends firing hashchange on the
document instead of a specific element when a user navigates to a URI
with a hash component.
Hi,
so I was reading the web sockets spec as well as a Firefox patch to
implement it.
Is it intentional that it is impossible to implement this spec over an
existing HTTP stack, as currently specified? In particular, due to the
strict requirements on the headers to send, it seems like you can't
http://www.whatwg.org/specs/vocabs/current-work/#examples
The Jack Bauer example has validation issues (using http://validator.nu/)
My fix:
--- jack.html.orig 2009-11-17 11:03:03.0 +0100
+++ jack.html 2009-11-17 11:03:19.0 +0100
@@ -41,12 +41,12 @@
you're interested in
With a nod to HTML5... ;)
*Want to win a trip to South By Southwest 2010? Or maybe a Flip Mino video
camera? Read on...*
*Open Video in 60 Seconds* http://contest.openvideoalliance.org/
The Open Video Alliance is holding a video
contesthttp://contest.openvideoalliance.org/.
To enter, just make a
