Out of curiosity, what are you doing with such a simple site (and I don't mean that in a bad way) that requires any conscious effort to fix? It seems like you really need to go out of your way to fuck up the back button and for a fix to be "work".

But, recent nuanced trends in web design/navigation aren't my top skill, so I'm asking the question honestly.

The site is built with the meteor framework, so it's not just the simple implementation you might expect from the layout. I imagine the features of meteor are useful in the actual app itself, which is probably not a simple site.

Basically, wrong tool for the job. The top page should probably be static, no need to involve meteor at all.

The rest? Maybe meteor is the best choice, cannot really say.

Honestly, I've been taken a bit by surprise that the back button bug has been such a big issue. I did some testing among friends (with a group of five or so startup, programmer types) and, believe it or not, it never came up.. That said, it'll be fixed in short order.

To the other comments, the service is considerably more complex (and yes, built on Meteor, MongoDB and ElasticSearch) as it serves up search results and updates in real time. Though the UI is simple, it does take a fair bit of effort to organize all the browsing information and index such that search results are relevant.

Don't mess with the back button and with the scrollbar.

Why not just elasticsearch ?

If you store texts in mongodb, look later for tokumx that compresses data.

It looks like you're using InstantClick. Make sure you're implementing it right.