[forwarded from http://psf.upfronthosting.co.za/roundup/meta/issue4]

When browsing issues resulting from a search, it would be nice if there were next/prev links on each issue, so that one could go through the search results without having to return to the result's index.

In Mozilla, this feature is provided as a set of links, looking like this:

Bug List:  (12 of 200) First  Last  Prev  Next   Show last search results

Apparently, it uses a cookie to implement a per-user latest bug list, however, there are certainly alternative approaches to provide that feature.

I've tried to come up with a patch that implements the "search
navigation" functionality in the classic tracker. What it does:

* The SearchAction creates a unique ID for each search and creates an
entry in the user's session that remembers the search URL for the
created unique search ID.

* The issue.index page stores the search result in the session, using
the search id as a key.

* The issue.item page, when coming from the issue.index page, adds
additional links to the page to:
 - go to the previous match
 - go to the next match
 - return to the search result

The search ID is passed on from the index page to the item page by
adding a variable to the GET request. This makes the URLs a bit ugly,
but is required so that multiple searches in multiple browser tabs don't
get in each other's way.

Please review & comment!

Philipp,
Thanks for the patch! This is a neat implementation, but I'd rather
achieve the same goal with less data in cookies.

IIUC, the issue.item page has the search URL embedded, but once you lose
the cookie you'd have to perform a SearchAction to be able to navigate
after clicking Next/Previous?

Also, I'm developing against 1.4.2, which doesn't have client.session_api :(

I think we can pass both IDs and the pointer in the URL, looks ugly but
is easy to share/bookmark/whatever :)

Daniel

http://psf.upfronthosting.co.za/roundup/meta/issue4 has been set to
resolved by ezio.melotti today.
subscribed myself.