- Article Type: General
- Product: Voyager
- Product Version: 8.1.1
Bug Report Form for 16384-2641
Release(s) replicated in: 7.0.1
Server Platform(s) affected: All
Browser type & version (if WebVoyage): FF2, IE7
Loss of functionality from (previous version, if applicable): N/A
Expected Results: Browser’s “back” button would not confuse the session after conducting a redirect search from a record page.
Actual Results: When you conduct a search, select a record, click on a link to a title/author/subject/etc. search then use the “back” button, WebVoyage thinks that the record you’re viewing is from the redirect search; clicking “next” and “previous” shows results from the redirect search, rather than the search that turned up the record in question.
Workflow Implications: “Back” button leads to confusing results when navigating results sets.
1) Conduct a basic search for “blue”
2) Select the 2nd result
3) From the record page, click on a search redirect (subject, author—whatever conducts a new search)
4) Note the results on that page, then click the browser’s “back” button to return to the record
5) Click the “Next” and “Prev” buttons (upper right of the window) to navigate to other results.
At this point you’ll be navigating through the results of the redirected search. The expected behavior would be to navigate through the results of the original search.
Other Information: In Classic, the “back” button was never supported for session-based craziness. Because sessions are handled differently now, it’s unclear what the status of the back button is in terms of “working as designed”ness.
Fixed in WebVoyage for 8.1.1.
- Article last edited: 3/7/2015