Works sweetly now.

Jason's changes in Stripes-connect have substantially fixed this. At least, there is no behaviour left that is "wrong".

But it's ugly that when you start typing in a new search, the currently displayed record vanishes. So I'll have a go at fixing that, too.

There are two problems, both of them I think related to the different URLs used by search and single-record display. Those URLs are, respectively:

• http://localhost:3000/users?query=river

• http://localhost:3000/users/view/6AC4EF66-90CE-4215-BDB3-9DC3106DC010

As a result, clicking on the record found by searching takes you to a distant full-record-view page where your search-term is no longer kept in the box; and from a full-record page, starting a new search takes you back to a distant URL where the first character you typed is discarded and you have to start again.

It's nice to think that both of these problems might be fixed when we properly adopt the hybrid URL scheme that we arrived at in , so that we use:

• http://localhost:3000/users/view/6AC4EF66-90CE-4215-BDB3-9DC3106DC010?q=river

when clicking on a search-result. That may involve some more trickery in the routing.