Look at this cool HTML5 website

[Ark]

The one who did this is a genius.

http://baroque.me/

the strings get longer so the notes also changes, just amazing!

[Jackolantern]

Wow, very cool!

I wonder how they are getting around the 1-sound-at-a-time limit? I know there are ways around it (Impact JS does it, too), but I just wonder the method.

[fang]

He's using the soundmanager library with flash sound: http://www.schillmania.com/projects/soundmanager2/

[Jackolantern]

Ahh, I gotcha. Isn't there some native HTML5 solution, though? Anything in Flash won't work in iOS.

[Chris]

I heard Google were working on a fix for the one sound at a time problem. Shouldn't be anything major so I would expect chrome to have better support soon.

One thing I am missing with HTML5 is decent webcam and microphone support (media capture). I think they are holding it off as there won't be any peer-to-peer networking support, but I still think there should be native functionality for webcams as I came up with a good Idea I'd like to try out.

[Jackolantern]

I thought I read once that the lack of webcam and microphone support was a security issue. Someone could run a page that doesn't display the webcam or microphone feed on the page, and then route the feed through a websocket without the user knowing to literally spy on them lol.

Honestly, some of the "security concerns" brought up by the WHATWG are kind of silly.

[Chris]

The way Flash works is by first asking the user if they want to allow webcam access to the application. A simple solution would be if browsers could throw up a disclaimer for the user to accept.

[Jackolantern]

That is what I thought, too, but apparently the WHATWG is against pop-up authorization as much as possible. I guess they are worried about a web environment where Flash has died, and all ads are served through HTML5, with 8 ads on a packed page all asking the user for 3 - 5 authorizations to draw attention to their ad. Flash has built-in protections against this, so maybe they will adopt something similar. Otherwise, I don't know how Websockets are going to get unblocked in everyone but Chrome, because apparently Mozilla, Apple and others don't trust it. They seem to be waiting on some kind of pop-up authorization method.