even worse is that there is no cached video while seeking. Even seeking to a "loaded" part of the youtube video results in the reloading the video from that point. Rewinding 10 seconds results in having to reload the video, wtf?
Support for the progress element is still missing from a lot of browsers, so I don't know if it's right to say that the markup is "wrong" for not using it
I like it. Just remember if you use this in production, save $("#progress") in a variable in the ajaxStart function to improve performance (this will call Sizzle one less time usually).
[+] [-] thejosh|13 years ago|reply
I'm on a fast connection so normally youtube loads instantly anyway, but this new method takes 4-10 seconds.
[+] [-] dm2|13 years ago|reply
[+] [-] X4|13 years ago|reply
I am using a kde widget called adjustable-clock which uses html5/css3/javascript and qml to render my system clock.
Here's the source for the current clock I use, it uses a progressbar for the seconds: http://htmlpaste.com/7e957bb5523fa58f98b6657073c4a544942a13c...
QML:
[+] [-] mistercow|13 years ago|reply
[+] [-] ynh|13 years ago|reply
[+] [-] pstadler|13 years ago|reply
It's fairly simple but it took some time to figure out the right sequence and timing for it to run smoothly across all devices / browsers.
[+] [-] druska|13 years ago|reply
[+] [-] zemaj|13 years ago|reply
Plenty of interesting ways that kind of bar could be included in a site.
[+] [-] paulfarino|13 years ago|reply
[+] [-] ezraroi|13 years ago|reply
[+] [-] BaconJuice|13 years ago|reply