Looks very much like http://errorception.com to me. Definitely a dense market now, a comparison page would help.

If there is a feature to be added, this is the one. On track. Thanks :)

I started with replaceState only, but later I realized there was no specific gain that I was having (other than slightly good looking string without hash). This method also suffers from reload and favicon flashes. If it reliably doesn't log to history (unlike location.replace()), using it could be a good idea. But that also comes with a tradeoff of older browser support issues, which requires using external javascript APIs.

I see. Surprised to learn there were still issues as replaceState() (as with pushState) is purely a transformation in the URL path. There's no reload and no update of the favicon link tag. Makes me wonder if that's a browser bug you saw.

What about detecting replaceState support and falling back to location.replace if necessary?

Is it? For changing the window location I am doing a location.replace which doesn't log to the browser history. What browser are you on?

Filled mine, too. Firefox 11.

I noticed it as well - I am using Chrome 20 (dev build) on Windows

Chrome dev/beta channel on osx. :)

Version 19.0.1084.36 beta

Does it? I am doing a location.replace() which doesn't log the URL to history.

It filled up my history as well. I'm on Chrome on a macbook. I love the idea!

Weird! I am unable to reproduce the issue. I am wondering if the problem is with some specific version of browser.

If it helps you in debugging, I am running chrome 18 on Fedora Linux 64bit

Thanks. It appears that location.replace doesn't work in a similar fashion on every browser. I am looking into other methods of implementing, but they look uglier.

Thanks, fixed.

It uses soundManager for cross browser audio handling. It first tries with flash and fallbacks to html5 if flash is not available. Firefox with flash disabled wouldn't support mp3, and thus won't be able to play it. I am using SoundCloud api only to fetch streams.

Hmm, that's odd, I'm using Chrome 19.01 and have no other plugins running asides FlashBlock. Once I disabled flash block everything ran fine. Does this version of Chrome not support the HTML5 fallback?

Here's the Js error:

Uncaught TypeError: Cannot call method 'init' of undefined /beatbar/:75 (anonymous function) /beatbar/:75 f.event.dispatch jquery.min.js:3 f.event.add.h.handle.i

I'm using Chrome 20.0.1116.0 (canary) with the plugins blocked by default (play on click) and I'm getting the same error. Also the usual 'run all plugins on this page' option is not there.

I think soundManager requires some special handling for flashblock cases. I didn't test with flashblock on. Thanks for reporting the issue.

It doesn't seem to work in Safari with click2flash, either. Possibly because click2flash doesn't actually disable flash, it just requires a click -- but there's nothing to click on.

HTML5 fallback seems to work fine on Safari iPad

I settled with the standard character sets as I wasn't sure if the fancy unicode character would be available cross platform or not. I'll look for this possibility again. Thanks.

That's intelligent. CSS taking care of CSS.

This part was specially interesting:

/* These may not be "wrong", but let's bug you anyway. */

b:after, i:after, blink:after, marquee:after { background: green; content: 'Should you be using strong or em?'; }

They announced Git support in 2009 also, but that was an April Fool's joke. Link to that post: http://blog.bitbucket.org/2009/04/01/announcing-git-support/