The simplest case: A paginated index that offers an edit link, that returns to the current page of the index. The page number is stored in session.
Now the user opens the index in TAB 1, skips to page 5 and then duplicates the tab (TAB 2). In TAB 2, he skips another 5 pages and clicks edit for one of the entries - 10 is stored in the page attribute of session Then he opens TAB 1 again (with index page 5) and clicks edit for some entry - 5 is stored in the page attribute of session. Then he decides to go to TAB 2 and stores the object, expecting to return to index page 10 and wondering, why he ends up in page 5. In the case, that the edit form can refer some other subpage, stack like tracking can become a big deal. A quite cumbersome solution is, to store the page number in a hidden field, or in the store link of the edit form. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
