This approach, albeit nice, will be very difficult to implement.
TL's approach is that if you navigate directly to the reader URL, you don't have any context of where this page came from, e.g.
Code:
http://www.site.com/catalog-reader/items/ac2-ezio-limited-edition-action-figure.html
As you can see ONLY the items "alias" or "ID" is provided and there is no information to tell it which page it was coming from.
The Catalog list pages is actually just a single 1 page where various types of filters can be applied and then added to the URL as parameters. If you need to show which filters have currently been selected also on the reader page, then we have to store all the URL parameters (/category/toys/orderby/date_asc/) as well as the current item. This will make the URL very long and its not necessary to view the details of that item (redundant).
The best possible solution would be the Catalog Navigation Module, which is currently being worked on (for release with 2.0), where the current item will be highlighted inside a nav tree of a single field you have chosen to be your navigation, e.g.
[attachment=0:a9t360xv]catalognav.jpg[/attachment:a9t360xv]
Of course you can also simplify your situation, by making 3 reader pages, each UNDER the list as parent, which will then highlight the parent item. If they don't click "Go Back" then at least they can then click back to the "default" list page.
Bookmarks