Very cool. Do you know if it behaves correctly with caching (e.g. Forward/Back buttons)? Generally speaking, Javascript modifications to a page cause inconsistencies with what the user sees when Back is pressed (and it seems impossible to avoid this?), so I'm wondering if this is a caveat here as well.

For a while it has been possible to manipulate browser history with pushstate and popstate, including the URL that shows in the address bar. I believe that for a while now it has been possible to fully imitate a conventional website on a single "page." (A while ago, I worked on doing this on a job where we had to keep a websocket open at all times.)

I use Turbolinks on some smaller projects and it works fine. Doesn't break the back button or anything. (Turbolinks is similar to Instantclick but without pre-fetching on hover.)

I thought Chrome already does this natively. At least in the Google search results I think.