I'm using form and List ver. 5.0.2. 

I have seen the following counter-intuitive/undesirable behaviours that may be related, and am hoping that someone can help me to work around them.

Pagination

Example 1: You access the details for a row from the 3rd page of a paginated list.  When you click on the back arrow to return to the list, instead of returning to the 3rd page you are returned to the 1st page. I would think you should be able to browse back and forth through the details of multiple rows without having to find the right page over and over again.

Advanced Search

Example 1: You access the details for a particular row from a search result.  When you click on the back arrow to return to the list, instead of returning to the search result, you are retuned to the list (1st page if pagination is enabled) with no history of the original search. I would think you should be able to browse back and forth through the details of multiple rows in your search result without having to recreate the search over and over again.

Example 2: You access the details for a particular row from a search result. Within the details view the advanced search interface remains at the top of the record however it will not perform a new search on the previous list (i.e. it will not return you to the list view with new results), it will only perform a search on the particular record that you are viewing in detail view, and show or hide the details depending on the search value entered. I would think that either the search interface should be hidden in the detail view or it should perform a search on the original data, not the one result that is displayed in detail view.

I look forward to feedback from the group.

>> If you decide to render your list with an XSL script, it will use a XSLT based paging template which is based on query strings, not on view_state.

I believe that is what I am doing.  I have used the default "advancedtable" XSL Script. 

I have created a workaround for the issue of returning to a search result or master list page from the detail page by changing the back arrow code to be the Javascript back  ( history.go(-1)) but I can't see how to use paging and the search function at the same time (and they go toghether well as if you need one you usually need the other).

I have now noticed two other issues:

Search when not on page 1 of a paged list
I also noticed another issue that is very similar to the others I described in my intial post.  if you have a paged list (e.g. 8 pages) and you search from page 1, the search comprises all 8 pages of the list.  If you begin your search from another page (such as Page 2) I get no results and weird behaviours like the page is now listed as "Page 2 of 1" and then further down I see "First Previous 1" ("Next" & "Last" are greyed out).  This can't be "by design".

Search Results span more than 1 page
If I perform a search on a list and get back enough results that my results are paged, clicking to the "next" page wipes my search, and puts me on the next page of the complete list.  i.e. if I am on Page 1 of a 2 page search result, and click next, I am now on page 2 of 8 of the complete list.

I'm guessing that if I put my mind to it more issues would pop out.

The F&L module is amazing however if you have a large list the ability to combine the search and paging functionality is hugely valuable, and these behaviours from a useability perspective seem like major issues to me.

If you were me (and not a developer) how would ytou approach this problem to use "querystrings" if that is the issue here.  I can't imagine anyone would want to restrict the ability of a site users to browse through search results without having to reinitiate the search for every record.

I am a little stumped as to my next step.
 

Thanks Stefan.

Guess that's that until a future release.  Is there anything more you need from me in terms of formally submitting the bug or will you take it from here and (hopefully) try to get it adderssed in a future release?