Marnen Laibow-Koser wrote in post #961085: > I don't think that would work, unless you can keep track of the names of > your different cookies.
That's not necessary, since the data is contained in the page itself. If you clone such a browser tab, the data is cloned too and will be modified by subsequent requests without affecting the master copy of the cloned tab. > But don't ever do it; it's a ridiculous hack. > Just make all your URLs bookmarkable, OK, but take a look on the page source of an index containing a delete link: There they inject a form onclick into the page, containing some hidden field to submit data. This trick could be used to post the page local cookie data, if there is no form in the document; otherwise the problem can be solved by adding a new hidden field on server side. Rails is clever enough, to implement some generic code, that does this fully transparent to the programmer. > don't break the Back button, and the problem will go away. This is not always possible - as pointed out above. It will work for quite plane HTML pages, but not for more complex applications. -- 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.
