when entering a new search on the search page, the new result page should show the same search tab as the old one.
One option would be to pass the &tab parameter through to /query and back again (i.e. adjust the search controller as well as the search js).
Alternatively, we could hijack the search field on the search page altogether and just perform the default /query?q= in a parallel background fetch, ignoring it if it redirects to /search? (since we're already there) and redirecting otherwise. This would increase response speed for continued searches, but increase server load in case someone enters a shortcut on the search page.
when entering a new search on the search page, the new result page should show the same search tab as the old one.
One option would be to pass the
&tabparameter through to/queryand back again (i.e. adjust the search controller as well as the search js).Alternatively, we could hijack the search field on the search page altogether and just perform the default
/query?q=in a parallel background fetch, ignoring it if it redirects to/search?(since we're already there) and redirecting otherwise. This would increase response speed for continued searches, but increase server load in case someone enters a shortcut on the search page.